Hoping that we don't hit into

    Selenium::WebDriver::Error::NoSuchDriverError:
      invalid session id

Again.

Fix approvals section when merge requests disabled

Closes #11321

See merge request gitlab-org/gitlab-ee!12070

EE port of instance level kubernetes cluster admin interface

See merge request gitlab-org/gitlab-ee!10761

Add bridge relation between Pipelines and Bridges

See merge request gitlab-org/gitlab-ee!11264

Allow replying to an individual note in the API

See merge request gitlab-org/gitlab-ee!12307

Additional fix to handle NULL lock_version

See merge request gitlab-org/gitlab-ce!28153

Bump clair-local-scan to v2.0.8

See merge request gitlab-org/gitlab-ee!12091

Backport members SCSS changes

See merge request gitlab-org/gitlab-ce!28115

Fix placement of LDAP icon in members list

Closes #8300

See merge request gitlab-org/gitlab-ee!12304

Resolve "Add filtering to project dashboard [FE]"

Closes #56992

See merge request gitlab-org/gitlab-ce!25231

Add filtering to project dashboard fe ee

See merge request gitlab-org/gitlab-ee!11209

Fix update head pipeline process of Pipelines for merge requests

See merge request gitlab-org/gitlab-ce!28057

Remove superfluous permission check for alerts

See merge request gitlab-org/gitlab-ee!12313

The policy `read_prometheus_alerts` already makes sure that the user has
at least maintainer access.

Add some missing specs to cover unprivileged access.

If the UI sends a string value for lock_version (e.g. "0"), then the
previous monkey patch did not properly handle that properly. This
commit casts the value to an integer to determine whether to look for
NULL lock_versions.

For merge requests, GitLab sends a POST request to
`namespace/project/merge_requests/:iid` with the
`merge_request[lock_version]` parameter with a string `0`. The string
value comes from the form field, which explains why
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28145 wasn't
sufficient.

Correct repo mirror SSH key generation docs

See merge request gitlab-org/gitlab-ce!27998

Correct repo mirror SSH key generation docs

See merge request gitlab-org/gitlab-ee!12117

The method already existed under a different name

Add issue template for refactorings

See merge request gitlab-org/gitlab-ce!27889

Fixes 'Broken master: rspec ./ee/spec/models/epic_spec.rb'

Closes #11513

See merge request gitlab-org/gitlab-ee!12344

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11513

CE Add leave link to access_granted email

See merge request gitlab-org/gitlab-ce!27892

Leave project/group from access granted email

Closes gitlab-ce#59421

See merge request gitlab-org/gitlab-ee!11941

(CE Port) New user onboarding (Welcome screen)

See merge request gitlab-org/gitlab-ce!28062

- Add styles for blue popovers
- Add render_if_exists to help menu for "Learn GitLab" menu item

New user onboarding (Welcome screen)

See merge request gitlab-org/gitlab-ee!11492

- Add "Learn Gitlab" item to help menu
- Add onboarding endpoint
- Add feature flag helper
- Add styles for blue popovers
- Move controller and template to /ee
- Update PO file
- Add changelog entry

Resolve "Support Prometheus for group-level clusters"

Closes #51963

See merge request gitlab-org/gitlab-ce!27280

EE Backport: Support Prometheus for group-level clusters

See merge request gitlab-org/gitlab-ee!10868

Compute resolver complexity based on items

Closes gitlab-ce#58408

See merge request gitlab-org/gitlab-ee!11575

If a field is a resolver, its complexity is automatically
increased. By default we add extra points for sort and search
arguments (which will be common for various resolvers).

For specific resolvers we add field-specific complexity, e.g.
for Issues complexity is increased if we filter issues by `labelName`
(because then SQL query is more complex). We may want to tune these
values in future depending on real-life results.

Complexity is also dependent on the number of loaded nodes, but only
if we don't search by specific ID(s). Also added complexity is limited
(by default only twice more than child complexity) - the reason is
that although it's more complex to process more items, the complexity
increase is not linear (there is not so much difference between loading
10, 20 or 100 records from DB).