Add warning for file addition of controller specs to Danger

See merge request gitlab-org/gitlab!50566

Upgrade Rails to 6.0.3.4

See merge request gitlab-org/gitlab!50480

Add script to verify migration rollback

See merge request gitlab-org/gitlab!49255

Add a new script that can be run in CI to verify that migrations added
in a merge request cleanly rollback to the previous known database state
on the target branch.

Remove devops_adoption_feature flag

See merge request gitlab-org/gitlab!50826

Add sorting by column in DevOps Adoption table

See merge request gitlab-org/gitlab!50743

Refactor Jira connect API calls to use axios

See merge request gitlab-org/gitlab!50746

Moves widget Gitaly call from page load to an async request

See merge request gitlab-org/gitlab!50286

Block assign quick action for test cases

See merge request gitlab-org/gitlab!50396

This commit remove thes devops_adoption_feature feature flag.
The flag was defaulted to true in 13.7 and is now being
removed in 13.8.

Add metrics yml files for usage data metrics definition

See merge request gitlab-org/gitlab!49126

  - Add examples for metric definition
  - Use json schema validator
  - Use method_missing for defining methods for attributes

Remove inactive integrations indicator in index and show pages

See merge request gitlab-org/gitlab!50753

We previously showed the "power" icon in the integrations
listing when an integration is not active. This UI polish
removes this so we only show a green check icon when
the integration is active.

Deprecate prometheus.listen_address and prometheus.enable

See merge request gitlab-org/gitlab!50500

We introduced `prometheus.server_address` setting in `gitlab.yml` which
is to be Rails application's SSOT regarding a Prometheus address.
Hence, we can deprecate the existing settings `enable` and
`listen_address`.

Changes:
* To `Gitlab::Prometheus::Internal` class methods:
  * `server_address` method renamed to `uri_without_protocol`, to
    reflect what the method actually does.
  * `listen_address` method renamed to `server_address`.
  * `promtheus_enabled?` method now depends on presence of
    `server_address`.

* To `Gitlab::DatabaseImporters::SelfMonitoring::Project::CreateService`
  class methods:
  * `prometheus_listen_address` method renamed to
    `prometheus_server_address`.
  * `internal_prometheus_listen_address_uri` renamed to
    `internal_prometheus_server_address_uri`.
Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

Fix base linter loading warnings

See merge request gitlab-org/gitlab!50397

Add rotation modal to create a new rotation and handle feedback

See merge request gitlab-org/gitlab!50268

Enable rotation creation in
on call schedules via
GraphQL with supporting specs

Improve Gitlab::Elastic::Indexer update logging  and document possible use of logs

See merge request gitlab-org/gitlab!50482

Refactor epic sort comparator for roadmap

See merge request gitlab-org/gitlab!50673

Resolve "Hide inoperable group search Releases filter - frontend"

See merge request gitlab-org/gitlab!50010

- **app/assets/javascripts/filtered_search/
filtered_search_token_keys.js:**
- **ee/app/assets/javascripts/filtered_search/
issuable_filtered_search_token_keys.js:**

Allow removal of specific filters.

- **app/assets/javascripts/pages/groups/issues/index.js:**

Don't show release filter.

- **changelogs/unreleased/remove-group-release-filter.yml:**

Changelog.

- **spec/frontend/filtered_search/
issues_filtered_search_token_keys_spec.js**:

Unit test.

Resolve "Forward an E-Mail to an existing issue as a new comment"

See merge request gitlab-org/gitlab!49050

- add email handler for forwarded emails
- expose new email address to UI

Remove ignored scanned_resources_count on Security:Scan

See merge request gitlab-org/gitlab!48723

Since we've always intended to have these various backup methods for
recovering data in our integration but we've never clearly documented
them we will write this down as a rough draft for now. If we are really
going to rely on this and encourage it's use we should also be testing
it and automating parts of it but that is more expensive and therefore
writing down what we know today is better than nothing.

These logs can be useful in the event of disaster recovery by replaying
the updates during a period of time from logging information. The
previous format was being blocked before ingestion into our logging
infrastructure likely due to the `wiki` field having an incorrect
format as field names cannot be re-used in our logs without them being
the same type. Either way this new format should not conflict and is
more machine readable than the previous one.

Migrates the alert on the new branch page

See merge request gitlab-org/gitlab!50307

Add link to support bot user docs

See merge request gitlab-org/gitlab!50792

Merge branch '256035-empty-changes-tab-on-merge-requests-should-not-show-file-browser-and-display-options' into 'master'

Hide file browser and display options from empty state changes tab

See merge request gitlab-org/gitlab!43467

- Also improves empty state text

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43467

- changelog

Moves the alert to use gitlab UI classes

Follow-up from "Fix project access token regression"

See merge request gitlab-org/gitlab!50800