Changelog: fixed
EE: true

Explain incompatibility between Code Owners and Global SAML memberships lock

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175999



Merged-by: Brendan Lynch <blynch@gitlab.com>
Approved-by: Joe Woodward <jwoodward@gitlab.com>
Reviewed-by: Joe Woodward <jwoodward@gitlab.com>

Update Gitaly version

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/176010



Merged-by: release-tools approver bot <project_278964_bot_77e28085fcec07f14dfd31c689824b5b@noreply.gitlab.com>
Approved-by: release-tools approver bot <project_278964_bot_77e28085fcec07f14dfd31c689824b5b@noreply.gitlab.com>
Co-authored-by: GitLab Release Tools Bot <delivery-team+release-tools@gitlab.com>

Migrate gl-text-green-500 -> gl-text-success

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/174422



Merged-by: Allison Browne <abrowne@gitlab.com>
Approved-by: Dan MH <dmizzi-harris@gitlab.com>
Approved-by: Scott de Jonge <sdejonge@gitlab.com>
Approved-by: Eduardo Sanz García <esanz-garcia@gitlab.com>
Approved-by: Allison Browne <abrowne@gitlab.com>
Reviewed-by: Scott de Jonge <sdejonge@gitlab.com>
Co-authored-by: James Rushford <jrushford@gitlab.com>

Merge branch '478175-merge-request-approval-policies-to-override-project-level-settings-not-reflected-in-mr-page' into 'master' 

Extend GraphQL with  policies overriding project approval settings in MR

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175614



Merged-by: Terri Chu <tchu@gitlab.com>
Approved-by: Terri Chu <tchu@gitlab.com>
Reviewed-by: Alexander Turinske <aturinske@gitlab.com>
Reviewed-by: Terri Chu <tchu@gitlab.com>
Reviewed-by: Martin Čavoj <mcavoj@gitlab.com>
Co-authored-by: Martin Čavoj <mcavoj@gitlab.com>

Changelog: added
EE: true

Introduced the Comment Temperature Vue component

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175980



Merged-by: Andrew Fontaine <afontaine@gitlab.com>
Approved-by: Jack Chapman <jachapman@gitlab.com>
Approved-by: Andrew Fontaine <afontaine@gitlab.com>
Reviewed-by: Denys Mishunov <dmishunov@gitlab.com>
Reviewed-by: Jack Chapman <jachapman@gitlab.com>
Co-authored-by: Denys Mishunov <dmishunov@gitlab.com>

Also re-named the buttons to not be bad/good

As per review

Snooze to-dos > Backend tweaks

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175163



Merged-by: Paul Gascou-Vaillancourt <pgascouvaillancourt@gitlab.com>
Approved-by: Thomas Hutterer <thutterer@gitlab.com>
Approved-by: Terri Chu <tchu@gitlab.com>
Approved-by: Jarka Košanová <jarka@gitlab.com>
Reviewed-by: Paul Gascou-Vaillancourt <pgascouvaillancourt@gitlab.com>
Reviewed-by: Suzanne Selhorn <sselhorn@gitlab.com>
Reviewed-by: Terri Chu <tchu@gitlab.com>
Reviewed-by: Thomas Hutterer <thutterer@gitlab.com>
Co-authored-by: Paul Gascou-Vaillancourt <paul.gascvail@gmail.com>

This check prevented previously snoozed to-dos from being snoozed again.

Merge branch '460271-refactor-groups_list_item-vue-and-projects_list_item-vue-into-shared-layout-component-2' into 'master' 

Refactor `projects_list_item` to `resource_list/list_item.vue`

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175497



Merged-by: Lorenz van Herwaarden <lvanherwaarden@gitlab.com>
Approved-by: Daniele Rossetti <drossetti@gitlab.com>
Approved-by: Lorenz van Herwaarden <lvanherwaarden@gitlab.com>
Reviewed-by: Ezekiel Kigbo <3397881-ekigbo@users.noreply.gitlab.com>
Reviewed-by: Daniele Rossetti <drossetti@gitlab.com>
Reviewed-by: Lorenz van Herwaarden <lvanherwaarden@gitlab.com>
Co-authored-by: Peter Hegman <phegman@gitlab.com>

- Add support for description slot
- Move description to its own component
- Add support for link to stat

Fix inconsistencies with `expires_at` access token

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175995



Merged-by: Jon Glassman <jglassman@gitlab.com>
Approved-by: Jon Glassman <jglassman@gitlab.com>
Reviewed-by: Isaac Durham <idurham@gitlab.com>
Co-authored-by: Eduardo Sanz García <esanz-garcia@gitlab.com>

Fix mistakes regarding what happens if `expires_at` is not defined in
two situations.

* Creating tokens: maximum allowable time
* Rotating tokens: one week

We use the same language everywhere for consistency.

Cleanup documentation links rubocop linters

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175656



Merged-by: Peter Leitzen <pleitzen@gitlab.com>
Approved-by: Peter Leitzen <pleitzen@gitlab.com>
Approved-by: Adam Hegyi <ahegyi@gitlab.com>
Co-authored-by: Paul Gascou-Vaillancourt <paul.gascvail@gmail.com>

Moves the `Gitlab/DocUrl` cop to the
`Gitlab/DocumentationLinks/HardcodedUrl` namespace.

Handle 404s when fetching GitHub user details

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175795



Merged-by: James Nutt <jnutt@gitlab.com>
Approved-by: James Nutt <jnutt@gitlab.com>
Co-authored-by: Luke Duncalfe <lduncalfe@eml.cc>

The GitHub API can return a `404` when we try to fetch the user's
details. We can see some errors when importing `rails/rails`.
Specifically for the user `Copilot`.

We already have a fallback of using the GitHub username as the source
user's name if we're unable to get the username from the API response.
https://gitlab.com/gitlab-org/gitlab/-/blob/331d2e9318220e6e229857aa4f0b7eb49e1e87ed/lib/gitlab/github_import/user_finder.rb#L133

This change does the same if we receive a `404` from the GitHub API.

Add container tag protection rules to project in GraphQL

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/174954



Merged-by: Radamanthus Batnag <rbatnag@gitlab.com>
Approved-by: Moaz Khalifa <mkhalifa@gitlab.com>
Approved-by: Eugie Limpin <elimpin@gitlab.com>
Approved-by: Radamanthus Batnag <rbatnag@gitlab.com>
Approved-by: Alex Buijs <abuijs@gitlab.com>
Reviewed-by: Radamanthus Batnag <rbatnag@gitlab.com>
Reviewed-by: Moaz Khalifa <mkhalifa@gitlab.com>
Reviewed-by: Zachary Painter <zpainter@gitlab.com>
Co-authored-by: Adie Po <avpfestin@gitlab.com>

This allows the tag protection rules to be fetched
via the project.

Changelog: added

Migrate to @gitlab/ui 105 & @gitlab/duo-ui 5

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175566



Merged-by: Artur Fedorov <afedorov@gitlab.com>
Approved-by: Julie Huang <julhuang@gitlab.com>
Approved-by: Artur Fedorov <afedorov@gitlab.com>
Reviewed-by: Jannik Lehmann <jlehmann@gitlab.com>
Co-authored-by: Jannik Lehmann <jlehmann@gitlab.com>

This commit  migrates to gitlab-ui 105 and
migrates duo-ui to 5
It updates the ai_agents codebase to consume DuoChat
via Duo-UI.

Update feature flag info for User Contribution Mapping in 3rd party importers

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175997



Merged-by: Ryan Lehmann <rlehmann@gitlab.com>
Approved-by: Magdalena Frankiewicz <mfrankiewicz@gitlab.com>
Co-authored-by: Martin Wortschack <mwortschack@gitlab.com>

Co-authored-by: Magdalena Frankiewicz <mfrankiewicz@gitlab.com>

[ci skip]

Move GraphQL mutations for branches into Bounded Context

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175831



Merged-by: Vasilii Iakliushin <viakliushin@gitlab.com>
Approved-by: Fred Reinink <freinink@gitlab.com>
Approved-by: Hunter Stewart <hustewart@gitlab.com>
Reviewed-by: Vasilii Iakliushin <viakliushin@gitlab.com>
Reviewed-by: Fred Reinink <freinink@gitlab.com>
Reviewed-by: GitLab Duo <gitlab-duo@gitlab.com>

**Problem**

`Branch::Create` and `Branch::Delete` mutations don't belong to the
existing bounded context.

**Solution**

Move both mutations under Repositories context.

Fix Layout/SpaceInsideParens offenses

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175990



Merged-by: Igor Drozdov <idrozdov@gitlab.com>
Approved-by: Igor Drozdov <idrozdov@gitlab.com>
Co-authored-by: Vitali Tatarintev <vtatarintev@gitlab.com>

Access tokens: Migrate HelpIcon to shared component

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175519



Merged-by: Eduardo Sanz García <esanz-garcia@gitlab.com>
Approved-by: Rahul Chanila <rchanila@gitlab.com>
Approved-by: Eduardo Sanz García <esanz-garcia@gitlab.com>
Reviewed-by: Rahul Chanila <rchanila@gitlab.com>
Co-authored-by: Sascha Eggenberger <seggenberger@gitlab.com>

Fix template variable literal

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175983



Merged-by: Miguel Rincon <mrincon@gitlab.com>
Approved-by: Miguel Rincon <mrincon@gitlab.com>
Co-authored-by: pkanellidis <pkanellidis@gitlab.com>

Changelog: other
EE: true

Move away from super.tap usage in user assignment creation

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175468



Merged-by: Matthias Käppler <mkaeppler@gitlab.com>
Approved-by: Serhii Yarynovskyi <syarynovskyi@gitlab.com>
Approved-by: Matthias Käppler <mkaeppler@gitlab.com>
Reviewed-by: Doug Stull <dstull@gitlab.com>
Reviewed-by: Matthias Käppler <mkaeppler@gitlab.com>
Co-authored-by: Doug Stull <dstull@gitlab.com>

Add and backfill namespace_id for issuable_slas

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175719



Merged-by: Adam Hegyi <ahegyi@gitlab.com>
Approved-by: Adam Hegyi <ahegyi@gitlab.com>
Co-authored-by: Shubham Kumar <shukumar@gitlab.com>

## What does this MR do and why?

Add and backfill namespace_id for issuable_slas.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/issuable_slas.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

## How to verify

We have assigned a random backend engineer from ~"group::platform insights" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/issuable_slas.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to `@tigerwnz` or @shubhamkrai.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

Ignore `stage` column from `CommitStatus`

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/173742



Merged-by: Marius Bobin <mbobin@gitlab.com>
Approved-by: drew stachon <730684-drew@users.noreply.gitlab.com>
Approved-by: Pedro Pombeiro <noreply@pedro.pombei.ro>
Approved-by: Marius Bobin <mbobin@gitlab.com>
Reviewed-by: drew stachon <730684-drew@users.noreply.gitlab.com>
Reviewed-by: Marius Bobin <mbobin@gitlab.com>
Reviewed-by: Pedro Pombeiro <noreply@pedro.pombei.ro>
Co-authored-by: Laura Montemayor <lmontemayor@gitlab.com>

Merge branch 'backfill-multiple-desired-sharding-key-small-table-bulk_import_export_uploads' into 'master' 

Add & backfill sharding keys for bulk_import_export_uploads

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175723



Merged-by: Adam Hegyi <ahegyi@gitlab.com>
Approved-by: Adam Hegyi <ahegyi@gitlab.com>
Co-authored-by: Shubham Kumar <shukumar@gitlab.com>

## What does this MR do and why?

Add and backfill multiple sharding keys for bulk_import_export_uploads.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/bulk_import_export_uploads.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

## How to verify

Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/bulk_import_export_uploads.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to `@tigerwnz` or @shubhamkrai.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillMultipleDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

Remove BackfillPCiPipelinesTriggerId

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175517



Merged-by: Marius Bobin <mbobin@gitlab.com>
Approved-by: Max Orefice <morefice@gitlab.com>
Approved-by: Marius Bobin <mbobin@gitlab.com>
Reviewed-by: Max Orefice <morefice@gitlab.com>
Reviewed-by: Tianwen Chen <tchen@gitlab.com>
Co-authored-by: Tianwen Chen <tchen@gitlab.com>