Since Ruby 2.7.2 comes with bundler v2.1.4 by default, we need to
upgrade the Gemfile.lock and bump the CI cache keys. We also need to
install bundler v1.17.3 to ensure a smooth transition for other
dependencies, like Gitaly.

Exclude development gems from QA bundle install since debaser doesn't
compile on Ruby 2.7.

This commit updates our GraphQL endpiont to allow releases to be
sorted by released_at or created_at.

Words describing ease-of-use shouldn't appear in documentation.
While that statement may seem outrageous and odd from a Product
view, it's an empathy issue at heart. As technical writers, we're
aware that what's easy for an experienced user can be complex and
frustrating (dare I say "hard"?) for new users, and telling a user
a seemingly-impossible task is "easy" causes cognitive dissonance
and frustration.

Rather than two overlapping and contradictory sets of instructions,
have one set of instructions for how to manage metrics dashboard
settings.

The page in the development directory is a stub and can be combined
with the information on the main Prometheus page.

Removed image-noshadow class from images.

Moved structure section back to ordered list.

  - Add license, settings, counts_weekly,
    top level keys to usage data
  - Add docs for placing metrics
  - Add change log file
  - This will make a basic structure to use
    for any metric added to usage data payload

This API is available on two levels: Project and Group.
A new field `container_repositories` is available on the Project object
and the Group project

Quote in wrong location

Enable GitHub Flavored Markdown support for issues to the
search autocomplete field. If the user is in the project
dashboard and enters GFM for an issue id, a link to that
issue will show up.

* Removes conditional feature flag code from specs
* Updates the docs to remove mention of feature flag
* Removes code from CommitStatus model
* Removes yml file with feature flag info

This changes repo location for Nginx Ingress, fluentD, and Prometheues
to vendored charts as the stable repo is scheduled to be deleted after
2020-11-13.

This adds a paragraph below the "Days to completion" header on the
group-level VSA page. The intent is to explain what the chart below
represents.

Users mistakenly think they can use the storage-specific settings and
plug in Azure connection settings. This doesn't work because Workhorse
uses a single credential to access multiple containers (aka buckets).

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/270948

Update doc/user/application_security/img/vulnerability_page_download_patch_button_v13_1.png, doc/user/application_security/img/vulnerability_page_merge_request_button_v13_1.png, doc/user/application_security/img/vulnerability_page_merge_request_button_dropdown_v13_1.png files

GitLab Core, both FOSS as well as unlicensed EE, can get instance
reviews.

If a user searches for a commit in a project and only finds
one result, redirect the user to that result. This already
exists for basic search and now is enabled for advanced
search. Added a notice explaining the redirect with a
link back to search results.

Bump this up from warning to error.

Make use of Vale 2.4.0 feature to strengthen
alert box rules

Needs https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/64495

When `false`, DAST uses the original target. When `true`, DAST will
reset a non-host target `http://test.site/some_path` to its host
`http://test.site`.

https://gitlab.com/gitlab-org/gitlab/-/issues/258805

Changed line length and used underscores for emphasis.