We were emphasising a point that's no longer true since we implemented
deploy tokens in 11.0 so rationalize the docs here.

In the example response we have builds with status `success` but the
property `runner` is null, which is not a realistic representation of
the response. The runner is always sent if the build has ran.

closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53121

Fixes #56864

Also refactors and combines resources and examples.

Also refactors structure of the page
to make the first section more useful.

- Pipeline status
- Job running
- Rollback button

Until we solve https://gitlab.com/gitlab-com/gitlab-docs/issues/347,
let's just be explicit to avoid confusion.

Merge branch 'restrict-jupyter-login' of https://gitlab.com/amit1rrr/gitlab-ce into restrict-jupyter-login

- Move instructions to use project templates to getting started
- Move the fork illustration into the in-depth guide
- Add screenshot for current project templates

Copyedit - better wording

Copy edit - typo

- Extract 445px as a variable
- Documentation changes: new image and update copy

Update the documented version requirement of Ruby inside of Upgrading
from Source to show GitLab 11.8 needs Ruby 2.5

Removed duplicate info.
Update pipeline health to cycle analytics.
Updated screenshots.

The documentations only covered the percentage based feature gates.
These don't work really well for a number of reasons, for example; a new
visual element in GitLab would be weird to see only 25% of the time.

Allowing feature gates based on projects and groups has been supported,
now it's documented.

copied from https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25633

This commit includes changes to add `UserAccess#can_create_branch?`
which will check whether the user is allowed to create a branch even
if it matches a protected branch.

This is used in `Gitlab::Checks::BranchCheck` when the branch name
matches a protected branch.

A `push_to_create_protected_branch` ability in `ProjectPolicy` has been
added to allow Developers and above to create protected branches.

Signed-off-by: NTakuya Noguchi <takninnovationresearch@gmail.com>

When `force` is set to `true` and `start_branch` is set, the
branch will be ovewritten with the new commit based on the
`HEAD` of the `start_branch`.

This commit includes changes to update the `gitaly-proto` gem.