Allow for schedule update
for oncall schedules via
GraphQL

Display schedule

See merge request gitlab-org/gitlab!48560

Use incident instead of issue for operation settings

See merge request gitlab-org/gitlab!48406

Gradually load more diffs as time goes on

See merge request gitlab-org/gitlab!48253

Resolve "N + 1: CommitDelta for large pushes"

See merge request gitlab-org/gitlab!46116

Make a note in the docs-lint links job bolded

See merge request gitlab-org/gitlab!49201

Refine group creation form

See merge request gitlab-org/gitlab!48490

Update nodejs-scan rule to wildcard prefix

See merge request gitlab-org/gitlab!48902

Check for pipeline first before status

See merge request gitlab-org/gitlab!49072

Migration to add project and issue permissions to issues in index

See merge request gitlab-org/gitlab!47819

Backfill issues documents with missing permissions
for project and issue permissions. Adds batch
capabilities to the Elastic::MigrationWorker
to support modifying large amounts of documents.

Add metrics for Clone quick_action

See merge request gitlab-org/gitlab!48537

Add negatable predicate methods

See merge request gitlab-org/gitlab!48242

Prior to this change, the matchers would need
in some cases to wait for the condition to return true and
the negate it. This can add up to 10 seconds each time.

This MR, instead of executing the page object's matcher method, uses
a custom matcher for match_when_negated that reads more naturally
and avoids using negative predicate methods such as has_no_file
in the end to end test.

Maintenance mode displays a banner message

See merge request gitlab-org/gitlab!44773

Geo: Ensure Reenqueuer works as intended

See merge request gitlab-org/gitlab!48172

Allow applicable approval rules to be included for reviewers

See merge request gitlab-org/gitlab!46855

Pass the 'raw' URL instead of 'blob' URL in revocation api call

See merge request gitlab-org/gitlab!49170

GitLab to Kubernetes communication blueprint

See merge request gitlab-org/gitlab!46847

Rebase against master, since this branch was a few weeks old, and
start by adding hard line wraps.

Fix typo in terraform state page

See merge request gitlab-org/gitlab!49185

e2e: Add missing let that led to a project being created when loading the file

See merge request gitlab-org/gitlab!48899

De-normalize project visibility_level into issues Elasticsearch documents

See merge request gitlab-org/gitlab!48436

Soften gitaly nfs warning

See merge request gitlab-org/gitlab!49172

Cleanup invitation_reminders experiment code

See merge request gitlab-org/gitlab!47920

Chunk deferred runtime and terminal modules in Web IDE

See merge request gitlab-org/gitlab!47719

Clarify why you may use Jenkins webhook option

See merge request gitlab-org/gitlab!48969

Fix bug in ProjectRepositoryStorageMove transition to scheduled

See merge request gitlab-org/gitlab!49105

Gitaly Cluster TLS doc fixes

See merge request gitlab-org/gitlab!49084

Previously transferring groups used custom code to trigger indexing
after the projects were updated. But this did not account for checking
visibility_level changes. As such we need to pass through the changed
attributes to maintain_elasticsearch_update when calling it directly so
we can determine if we need to also index the associated issues again.

This method will be used in several places as we de-normalize more data
in the index. This method at the class level also helps us avoid typo
like bugs or association rename bugs which would have previously
only have been caught later in sidekiq worker raising an exception.
Raising early when defining the class provides a safer developer
experience.

Since the `visibility_level` of issues will later be used for filtering
internal issues we need to ensure the value is correctly set.

This is necessary to search issues correctly without joining to the
parent project. The previous case where we only set
`issues_access_level` will not correctly handle "Internal" projects
because "Internal" does not change the `issues_access_level` of the
project and we need a way to ensure that issues from "Internal" projects
are only found by logged in users.