Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

[ci skip]

Closes #23460

When we added caching, this meant that calling `can_be_resolved_in_ui?` didn't
always call `lines`, which meant that we didn't get the benefit of the
side-effect from that, where it forced the conflict data itself to UTF-8.

To fix that, make this explicit by separating the `raw_content` (any encoding)
from the `content` (which is either UTF-8, or an exception is raised).

For each event with `Event#target_type` of "Note",
we had a query to load the associated instance `noteable`.

For example, if `Note` was related to an issue, we'd load each `Issue`
with its own query (N+1 problem).

Closes #43150.

Now the issuable reference check works only in project scope, if we
reference an issuable from a non-project resource (e.g. epics), then
project is not set, and there is mismatch in generated issue references.

This patch enables issuable reference state check also from group scope.

Closes gitlab-ee#4683
Related to #30916

These limits were updated in our docs, and in omnibus some time ago. But
the defaults in the source-install were missed.

See:

* https://github.com/rails/rails-html-sanitizer/releases
* https://github.com/flavorjones/loofah/releases

When the database is in a read-only state, display a banner on each
page informing the user they cannot write to that GitLab instance.

Closes gitlab-org/gitlab-ce#43937.

Closes #28857

Before we were using a "plumbing" Gitlab::Git method that does not go
through Gitaly migration checking.

[ci skip]

From
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5031#note_64372406

James Lopez authored 6 years ago and Mark Fletcher committed 6 years ago

[10.6] Fix GitLab Auth0 integration signs in the wrong user

See merge request gitlab/gitlabhq!2354

Douwe Maan authored 6 years ago and Mark Fletcher committed 6 years ago

Server Side Request Forgery in Services and Web Hooks

See merge request gitlab/gitlabhq!2337

Closes #44446.

Closes #44477

Closes #44298