[ci skip]

[ci skip]

[ci skip]

To clarify what's meant by "from a logical perspective" here, I
consulted Python's PEP8 style guide, which provides some helpfully
precise language: 

> Extra blank lines may be used (sparingly) to separate groups of 
> related functions. Blank lines may be omitted between a bunch of 
> related one-liners (e.g. a set of dummy implementations).

https://www.python.org/dev/peps/pep-0008/#blank-lines

I adapted this passage to the existing language for the newline rule.

[ci skip]

The wrong example for "Branches".
Added option parameters in protect branch section.
Here is reason: https://gitlab.com/gitlab-org/gitlab-ee/commit/3ab07b8aae8dae43cfa3aae1306c59ea264a8594

Maybe this section could/should be deleted. Because in file repositories.md it had been deleted:  https://gitlab.com/gitlab-org/gitlab-ee/commit/8f3701eff005aeedcebff8ce02074f5056a369b3

[ci skip]

These can't be resolved in the UI because if they aren't in a UTF-8
compatible encoding, they can't be rendered as JSON. Even if they could,
we would be implicitly changing the file encoding anyway, which seems
like a bad idea.

This allows web hooks to have a URL back to entities without having to
generate it themselves.

See also #19863.

Fixes #18458.

Versions 0.7.9 and 0.7.10 crash on previously valid 'authBackend'
settings.

Now the alias should be used as:

    git mr upstream 5

To check out a MR number 5 from the upstream remote, into a `mr-upstream-5`
local branch.

Also clarify that the `5` in the merge request is the number shown in GitLab.

The previous way was put under the
"By modifying `.git/config` for a given repository" section. The
disadvantage is that one has to modify `.git/config` for each repository
that one uses. The new way was put under the "By adding a git alias"
section. One has to create this git alias once, and then it will work
from any repository, without having to modify `.git/config` over and
over again.