Ignore user status emoji in assertion

Closes gitlab-org/quality/staging#45

See merge request gitlab-org/gitlab-ce!26085

Filter Jira shared secret from logs

See merge request gitlab-org/gitlab-ce!26077

Improve precision of group docs

Closes #58635

See merge request gitlab-org/gitlab-ce!25950

Reduce dangerbot message to the essentials

Closes #58231

See merge request gitlab-org/gitlab-ce!25585

Remove icon in activity only message on smaller screen widths

See merge request gitlab-org/gitlab-ce!26032

Removes EE differences for environments_app

Closes gitlab-ee#10079

See merge request gitlab-org/gitlab-ce!26030

Update spacers to increment 1 unit at a time

See merge request gitlab-org/gitlab-ce!26033

Refactor AutoDevOps test to one test with two expectations

See merge request gitlab-org/gitlab-ce!25836

Add table entries from EE docs

See merge request gitlab-org/gitlab-ce!25995

Add core-js polyfill for Promise.finally()

See merge request gitlab-org/gitlab-ce!25925

Fix health checks not working behind load balancers

Closes #58573

See merge request gitlab-org/gitlab-ce!26055

Seed tablesample strategy

Closes #58791

See merge request gitlab-org/gitlab-ce!25966

The change in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24199 caused
requests coming from a load balancer to arrive as 127.0.0.1 instead of
the actual IP.

`Rack::Request#ip` behaves slightly differently different than
`ActionDispatch::Request#remote_ip`: the former will return the first
X-Forwarded-For IP if all of the IPs are trusted proxies, while the
second one filters out all proxies and falls back to REMOTE_ADDR, which
is 127.0.0.1.

For now, we can revert back to using `Rack::Request` because these
middlewares don't manipulate parameters. The actual fix problem involves
fixing Rails: https://github.com/rails/rails/issues/28436.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58573

This produces stable approximate counts among invocations unless the
table changed.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58791.

Merge branch '58739-hashed-storage-prevent-a-migration-and-rollback-running-at-the-same-time' into 'master'

Hashed Storage: Prevent a migration and rollback running at the same time

Closes #58739

See merge request gitlab-org/gitlab-ce!25976

Backports EE change for expanded pipelines

See merge request gitlab-org/gitlab-ce!26043

Allow gitlab:ui:visual to fail

See merge request gitlab-org/gitlab-ce!26042

Cache Repository#root_ref within a request

Closes #58684

See merge request gitlab-org/gitlab-ce!25903

Fix counting of groups in admin dashboard

Closes gitlab-ee#7435

See merge request gitlab-org/gitlab-ce!26009

Resolve CE to EE differences in the lib/api directory

See merge request gitlab-org/gitlab-ce!25430

This is a small polishing on the storage migration and storage rollback
rake tasks. By aborting a migration while a rollback is already
scheduled we want to prevent unexpected consequences.

Remove some easy factories from migration specs

See merge request gitlab-org/gitlab-ce!26025

Remove fake repository_path response - resolved issue# 50386

Closes #50386

See merge request gitlab-org/gitlab-ce!25942

The repository_path is no longer needed since
https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/231, which closes
https://gitlab.com/gitlab-org/gitlab-shell/issues/135.

Authenticate the internal API using a header

See merge request gitlab-org/gitlab-ce!25924

When an empty project is loaded in the UI, there are 15 separate Gitaly
FindDefaultBranch calls to determine the root_ref. Previously, it was
not cached even within the request. This change caches it within the
request so only a single FindDefaultBranch RPC is needed.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58684

Update feature proposal template with "Intended users"

See merge request gitlab-org/gitlab-ce!25906

Revert "Merge branch 'gitaly-version-v1.28.0' into 'master'"

See merge request gitlab-org/gitlab-ce!26037