Fix typo in SHA attribute spec

See merge request !12717

#20628 Enable implicit flow in Gitlab as OAuth Provider

Closes #20628, #2716, and #19470

See merge request !12384

Include new URL helpers retroactively into includers of Gitlab::Routing

Closes #34821

See merge request !12716

Add gitaly_git_blob_raw feature

See merge request !12712

Allow to enable the performance bar per user or Feature group

Closes #33929 and #34528

See merge request !12362

Fixed jobs page not being in new admin sidebar

See merge request !12710

Added EachBatch for iterating tables in batches

See merge request !12707

Don't mark empty MRs as merged on push to the target branch

Closes #32800

See merge request !12711

Allow admins to retrieve user agent details for an issue or snippet

Closes #29508

See merge request !12655

Test logging in via the Authentiq OAuth provider in a feature spec

Closes #34737

See merge request !12694

Fixed text overflow issue in new sidebars

See merge request !12648

Moves alert boxes to below the breadcrumbs

See merge request !12631

# Conflicts:
#   db/schema.rb

Migrate Gitlab::Git::Repository#commit_count to Gitaly

Closes gitaly#355

See merge request !12688

Add variables to pipelines schedules

Closes #32568

See merge request !12372

Fix dashboard labels dropdown

Closes #34590

See merge request !12708

Native group milestones

See merge request !12280

Closes #20628 by re-enabling implicit grant in Doorkeeper config. OAuth2 documentation refactored. 

Speed up `all_commit_shas` for new merge requests

See merge request !12706

Resolve "Inconsistent location of members page between groups and projects"

Closes #29893

See merge request !11560

This module provides a class method called `each_batch` that can be used
to iterate tables in batches in a more efficient way compared to Rails'
`in_batches` method. This commit also includes a RuboCop cop to
blacklist the use of `in_batches` in favour of this new method.

N+1 problems on milestone page

Closes #34736

See merge request !12670

When we push to an MR's target branch, we check if the MR's HEAD commit is
contained in the push. This lets us mark MRs as merged if they were merged
manually.

However, we also added a feature where you can create an empty MR from an
issue. If that MR is created around the time of a merge to the default branch,
we would process the push after creating the MR, and consider it to be a manual
merge.

To fix that, we exclude empty MRs from this process. If they are empty, they
were empty before the push we're processing, so we shouldn't touch them!

This makes the `Boards::CreateService` more reusable for EE

See merge request !12704

Follow-up from "Namespace license checks for multiple assignees"

Closes gitlab-ee#2839

See merge request !12701

Refactor several javascript files to ES module syntax

See merge request !12683