These lines should say "prerequisites," plural.

This adds a note to protected branches and
target branch rules that they are case-sensitive.
It also adds documentation that provides a minimal example.

Changelog: fixed
EE: True

Because the left nav is changing
and will have a button instead
of carat, and no magnifying glass.

Related to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127935

Because we changed the way we
do the markdown.

Related to: https://gitlab.com/gitlab-org/gitlab-docs/-/issues/1690

Because we changed the way we
do the markdown.

Related to: https://gitlab.com/gitlab-org/gitlab-docs/-/issues/1690

Changelog: changed

This document will be removed soon, so let's remove the links now.

This documents how protected branch settings are applied when multiple
protected branches apply to a branch through the use of wildcards.

Make the subheadings easier to understand for newer users.

Make super clear about the most permissive rule.

When multiple `ProtectedBranch` records match a branch we check if any
of the records have `code_owner_approval_required` set to `true`.

https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/ee/gitlab/checks/diff_check.rb#L25
https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/models/ee/project.rb#L731
https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/models/concerns/ee/protected_branch.rb#L23

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/393187

Reverse the order to make a little clearer what version is available
to everyone, and what version is available to higher tiers. Also,
clarify that two particular fields have more selection available to
higher tiers.

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/410475

Users and groups can be selected only with GitLab Premium or Ultimate
license.

GitLab administrators now need to be explicitly granted permission
to modify protected branches or tags. This is a potentially breaking
change, so let's start adding in version history to the requisite
pages, and create a breaking-change notice.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/12776
Related to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117735

user/project/code_owners.md becomes
user/project/codeowners/index.md

This change provides scaffolding for splitting this page apart. It
was already unwieldy, and the new additions of syntax guides and
error handling have tipped it over the edge into unusability. Split
everything apart in a future MR; first, let's get it moved.

Fix future tense by changing it to present tense. Leave all other
edits for a separate commit.

Slightly more active verbs here.

Our style guidelines say not to use
https://docs.gitlab.com/ee/development/documentation/styleguide/word_list.html\#eg

Related epic: https://gitlab.com/groups/gitlab-com/-/epics/1940

Because the menu changed.
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/366082/

Let's update the docs to reflect the wording that needs to
change in the UI.

Make clearer that the most permissive rule wins.

These two pages for Code Review had incomplete information about
the history of the feature flag. I dug up the history, and built out
the version history notes in the way our team expects.

Move the admin and group-level default branch protection settings
from the general settings page to repoitory settings and update some
of the branch protection labels for clearer interpretation.

Changelog: changed

The feature flag warning is not needed