This would be much more accurate. We assume this is an
auto-generated email if such header is provided, and
the value is not "no". It could also be: "auto-generated",
"auto-replied", or other values from extension. It seems
that only "no" could mean that this is sent by a human.

See: https://tools.ietf.org/html/rfc3834

Also make it easier to have mailer helper

Update milestone docs CE

See merge request !13233

Expose target_iid in Events API

See merge request !13247

Extending API for protected branches

See merge request !12756

Add rugged_is_ancestor method

See merge request !13232

Fix Issue board when using Ruby 2.4

Closes #35769

See merge request !13220

Make the 'issuables list meta-data' shared example less dangerous

See merge request !13236

Ensure all project factories use `:repository` trait or `:empty_project`

See merge request !13238

Add filtered search to group issue dashboard

Closes #33575

See merge request !13167

Remove jQuery cropper plugin from vendors directory

See merge request !13239

Add kube_namespace and standardize common variables for additional metrics queries

See merge request !13169

Fix encoding error for WebHook logging

Closes #35815

See merge request !13230

Make Markdown autocomplete dropdowns style consistent

See merge request !13127

Derive project path from import URL

Closes #27341

See merge request !13131

Docs: update articles list

Closes #35800

See merge request !13229

Fixes the search losing focus

Closes #35515

See merge request !13221

This shared example would take an object's database ID and create a
number of objects based on it. If for some reason the ID were a high
number, like 20, this would create `20 + 21 + 22` objects.

Not only was this dangerous from a performance perspective, it was
entirely unnecessary, as the behavior it was testing is already
well-tested in the unit test for the underlying object. For a controller
test, which is what's including this shared example, all we need to do
is verify that the assigned object contains the correct `id => object`
Hash, which is what we now test for.

also, trigger build

Resolve "Remove `events` from `notification_settings`"

Closes #33620

See merge request !13152

Bump rubocop to 0.49.1 and rubocop-rspec to 1.15.1

Closes #34869

See merge request !12741

In Ruby 2.4, Hash#compact exists and returns a Hash, while in
Ruby 2.3,
Hash#compact is implemented by Rails and returns a new
`ActionController::Parameters` instance in this case.

Also, `ActionController::Parameters#compact` is deprecated in
Rails 5.1 so we're using `reject { |_, value| value.nil? }` instead.
Signed-off-by: Rémy Coutable <remy@rymai.me>

Add code review guidelines related to Build [CI skip].

See merge request !13223

Fix "API specs and linting failing on master"

Closes #35825

See merge request !13227

Make time span dropdown style on cycle analytics page consistent

See merge request !13183