GitLab

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

- Pipeline status
- Job running
- Rollback button

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

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

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.

The API get projects/:id/traffic/fetches allows user with write
access to the repository to get the number of clones for the
last 30 days.

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

Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.

For consistency, also ensure entries in the list
are aligned when they span multipls lines.