Docs: Troubleshoot Geo "Error syncing repository"

See merge request gitlab-org/gitlab!47057

Clarify separate Object Storage buckets in docs

See merge request gitlab-org/gitlab!54075

Updates the note on separate Object Storage buckets
to call out that the same one can now be used generally
unless using Helm.

Improve profile status emoji alignment

See merge request gitlab-org/gitlab!54078

Epics list using `issuable_list` [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!46769

Remove obsolete DOMContentLoadedEventListener

See merge request gitlab-org/gitlab!53875

Feature Flag group attribution for Manage

See merge request gitlab-org/gitlab!52876

Schedule user status cleanup [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!53620

Tweak doc intro wording

See merge request gitlab-org/gitlab!54074

Mention object storage in Sidekiq and Rails reference architectures

See merge request gitlab-org/gitlab!50852

Avoid creating repository when calling Wiki#empty?

See merge request gitlab-org/gitlab!54062

Enable dast_saved_scans feature flag by default

See merge request gitlab-org/gitlab!53942

Merge branch '300143-jira-integration-fe-on-a-project-s-vulnerability-report-show-count-of-related-jira-issues' into 'master'

JIRA Integration - On a project's vulnerability report, show count of related Jira issues within a rows activity column

See merge request gitlab-org/gitlab!53321

Show merged version of ci config [RUN AS-IF-FOSS] [RUN ALL RSPEC]

See merge request gitlab-org/gitlab!53299

- This adds a tab that shows the merged yaml result
  inside the pipeline editor section. Also adds tests
  and move the text editor and new component inside a
  sub-folder

Clean up glTooltips feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!51345

Remove facade that switches between Bootstrap
tooltips and GitLab UI tooltips. As a result
the only living implementation in the app for
tooltips components will be GitLab UI

Docs: Clarify that referenced issues in MRs are not auto-closed

See merge request gitlab-org/gitlab!53986

BulkImports: Use Pipeline::Context as Pipeline attribute

See merge request gitlab-org/gitlab!54007

Clean up feature_flag_contextual_issue feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!53816

Adds `epics_list` app to render Epics list
by using `issuable_list` internally.

Add daily coverage data new finder [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!53670

This commit introduces a new finder which will be used to
fetch our daily coverage data at the project and group level.

Extract project push rule to service class

See merge request gitlab-org/gitlab!53733

Docs: Clean up background migration checking Ruby snippets

See merge request gitlab-org/gitlab!53877

This MR implements scheduled user status cleanup.

- Adding `clear_status_at` column to `user_statuses`
- Add index to `clear_status_at` to easily query the statuses that needs
  cleanup
- Add cronjob that looks for relevant records and invokes the cleanup

Add changelog EE argument to table

See merge request gitlab-org/gitlab!53943

Remove unused feature flag YML files [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!54044

Improvements to terraform state storage setup

See merge request gitlab-org/gitlab!53245

Reduce the boilerplate of passing the context as parameter to a lot of
internal methods in the Pipeline::Runner.

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/321291

Push rules can be treated as a type of settings, such as
application_settings, project_settings, etc. There must be only one for
a given project. Therefore, it would be better to just expose the update
interface and let the creation handled behind the scene.

This commit extracts project push rule create and update logic to
a dedicated service class. This change allows to centralize auditing
and logging of actions from Project Push Rule controller and API.

The POST and PUT API can handle both create and update without raising
`unprocessable_entity` and `not_found` error respectively. Since the
user can only manage push rule via project id and they can only ever
create one, this change reduces coordinating POST request before PUT
request.

Handle severity for generic payloads more gracefully

See merge request gitlab-org/gitlab!53999

Also add to 2k