Fix button inconsistencies on blob header

See merge request gitlab-org/gitlab!47571

Add email notifications for CSV requirements import

See merge request gitlab-org/gitlab!46484

Add project support to Invite Members modal

See merge request gitlab-org/gitlab!44785

Use Gitlab::Http as the adapter for Graphql queries

See merge request gitlab-org/gitlab!47444

Improve the look of wikis in search results

See merge request gitlab-org/gitlab!47470

Update dependency @gitlab/eslint-plugin to v4.1.0

See merge request gitlab-org/gitlab!44164

Show and link group path for saml provider

See merge request gitlab-org/gitlab!47563

Fix kwargs deprecation warnings in merge request resolver specs

See merge request gitlab-org/gitlab!47533

Deduplicate epic iids and add uniqueness constraint

See merge request gitlab-org/gitlab!47081

Add cloud_license_auth_token to ApplicationSettings

See merge request gitlab-org/gitlab!47396

Remove unused scoped labels feature flag

See merge request gitlab-org/gitlab!46964

Fix pipeline security tab filters not showing

See merge request gitlab-org/gitlab!47294

Merge branch '259605-repositories-gone-after-update-broken-migration-to-hashed-storage' into 'master'

Hashed Storage: make migration and rollback resilient to exceptions

See merge request gitlab-org/gitlab!46178

Fix config variables when having includes

See merge request gitlab-org/gitlab!47189

Add new fields for creating issues from vulnerabilities in Jira

See merge request gitlab-org/gitlab!46982

This change adds new fields vulnerabilities_enabled and
vulnerabilities_issuetype to JiraTrackerData to allow user to configure
Jira for vulnerabilities.

When implementing config variables, we did not pass necessary parameters
to yaml processor.

Resolve "Set Auto-Stop Environment Expiry Period when an environment is created"

See merge request gitlab-org/gitlab!47239

Add and update QA text content matchers

See merge request gitlab-org/gitlab!47351

- Adds a negatable have_text/have_content matcher to be used instead
  of Capybara's built-in ones
- Include all custom matchers during RSpec config. This should make it
  simpler to add more matchers - we just need to put them in
  qa/spec/support/matchers in the Matchers module
- Update a few tests that used `expect(page).to have_content`

Update code stage calculation in VSA

See merge request gitlab-org/gitlab!47215

This change updates the calculation in value stream analytics. For the
code stage, the start event timestamp can be first_commit_at (new) or
first_mentioned_in_commit_at.

The change also introduces a separate stage where only the
first_commit_at is used.

Extend require_migration helper on EE

See merge request gitlab-org/gitlab!47509

Documentation: Add dos-and-donts for resolver re-use

See merge request gitlab-org/gitlab!47325

Add documentation for the Canary Ingress Weight Change

See merge request gitlab-org/gitlab!45637

This commit adds the documentation.

[GraphQL] Boards: use Global-ID scalar

See merge request gitlab-org/gitlab!36113

Fix an issue in the create_empty_index rake task

See merge request gitlab-org/gitlab!47575

Update detailed_metric.vue modal to match Pajamas guidelines

See merge request gitlab-org/gitlab!46183

Attempts to start the process of updating the detailed_metric.vue
file to use the new Pajamas components. It is neither correct nor
complete.

Update `ci_jwt_signing_key` feature flag to be enabled by default

See merge request gitlab-org/gitlab!47336

This updates the `ci_jwt_signing_key` feature flag to be enabled by
default.

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

User admin approval - Email admin the access request

See merge request gitlab-org/gitlab!46895

Point DS doc to correct issue for SBT 1.3+ support

See merge request gitlab-org/gitlab!47569

Fix internal lfs_authenticate API for non-project repositories

See merge request gitlab-org/gitlab!47404

This endpoint is used for LFS over SSH and had two problems:

1. We were generating the repository URL from `project` rather than
   `container`, which means we'd return the wrong URL for e.g. project
   wiki repositories.

   In practice this didn't break LFS, as we're not touching the
   repository itself and just associating the objects with the project
   record, which works the same with project wikis.

2. We did not check if LFS is enabled, which means we'd still return a
   URL for project snippets. This is less of a problem as the subsequent
   HTTP requests to the LFS controllers would still fail, but it's
   better to be consistent and abort early here.

Follow-up to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/45874