The pipeline suggest 1st nudge starts on the merge request, so:

- the 1st nudge was changed to pass the merge request path from
the 1st to the 2nd/3rd nudge.

- the 3rd nudge was changed to set the Merge request path into
the cookie set when clicking the Commit Changes button.

- the 4th nudge then checks for the cookie name instead of just
the cookie existence. The merge request path is used for the new
button. If they happened to have an old cookie, it links to the
project merge request list instead.

Update dependency @sourcegraph/code-host-integration to v0.0.50

See merge request gitlab-org/gitlab!39199

Lock award emojis when issuable is locked

See merge request gitlab-org/gitlab!40150

Update to glbutton in manual job variables form

Closes #219799

See merge request gitlab-org/gitlab!39311

Update GitLab UI/SVG

See merge request gitlab-org/gitlab!40271

Remove title and description ignore rule

Closes #217587

See merge request gitlab-org/gitlab!39728

Remove useless stubs for components

See merge request gitlab-org/gitlab!40207

Convert gl-deprecated-button to gl-button in dropdown_header.vue

Closes #219780

See merge request gitlab-org/gitlab!38815

Add details regarding debugging options for BitBucket server imports

See merge request gitlab-org/gitlab!40037

RUN AS-IF-FOSS: Resolve "Find better place for app/models/*enum.rb modules"

Closes #202207

See merge request gitlab-org/gitlab!39691

[RUN-AS-IF-FOSS] Remove and deprecate gl_dropdown jQuery function

See merge request gitlab-org/gitlab!39897

Migration batch comment finish review loading button

Closes #229337

See merge request gitlab-org/gitlab!39521

Enable to delete a value stream

See merge request gitlab-org/gitlab!40127

But only if it is not default value stream
Expose is_custom field on value stream

Move enums related modules to a separate directory

Move enums related modules to a separate directory

Move enum related modules into a separate directory

Moves enums modules into a separate directory

Move enums related modules into a separate directory.

Merge branch '240938-schedulecalculatewikisizes-when-missing-wiki-sizes-exist-calculates-missing-wiki-sizes' into 'master'

Fix a broken background migration spec due to a missing column

Closes #240938

See merge request gitlab-org/gitlab!40290

Update application limits documentation for the package registry

See merge request gitlab-org/gitlab!40292

Enable dast nightly fullscan

See merge request gitlab-org/gitlab!38253

This will remove the stage review-after
Will trigger DAST data seeding when DAST_RUN is true
Dast data seeing added to review-deploy job

Use bar generated data instead of hardcoded data

See merge request gitlab-org/gitlab!40238

Create instance-level security charts component

See merge request gitlab-org/gitlab!40046

- create separate components just for the instance-level security
  charts
- modify the init file to use the component
- update CSS of severity component
- add tests

Add project code search to search documentation

Closes #30653

See merge request gitlab-org/gitlab!39591

Signed-off-by: Rémy Coutable <remy@rymai.me>

Merge branch '219781-replace-gl-deprecated-button-with-gl-button-in-ee-app-assets-javascripts-subscriptions-new' into 'master'

Replace <gl-deprecated-button> with <gl-button> in subscriptions/new/components/checkout/confirm_order.vue

See merge request gitlab-org/gitlab!40119

Remove Icon component from vue_shared

See merge request gitlab-org/gitlab!38777

Include Redis in Workhorse-in-test-suite integration

Closes #209245

See merge request gitlab-org/gitlab!40276

Fix missing pipeline e-mails when job logs moved to object storage

See merge request gitlab-org/gitlab!40075

As discussed in https://gitlab.com/gitlab-org/gitlab/-/issues/195430,
it's possible that a race condition occurs when a build finishes and a
failed pipeline email goes out. This is what was happening before:

1. Build finishes and causes a pipeline failure. The pipeline failure
transition causes the pipeline to run `PipelineNotificationWorker`,
which schedules an `ActiveJob` to e-mail a user with a failed pipeline
ID.

2. `BuildFinishedWorker` schedules `ArchiveTraceWorker` to move the job
log, stored locally on a filesystem, to object storage.

3. The `ActiveJob` runs and loads the pipeline and failed build
logs. Some builds have been moved to object storage, but the `ActiveJob`
has a stale record and attempts to load the file from the filesystem.

4. The file doesn't exist, an `Errno::ENOENT` exception is raised.

To fix this, we now attempt a refresh the job from the database if we
encounter this exception.