[ci skip]

I replaced "merge requests" by "commits". As far as I notice, merge requests per se don't trigger CI; commits and pushes (which are essentially adding commits) do. This is logical: an MR doesn't create anything new, so there is nothing to test.

[ci skip]

Took it from https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3232

[ci skip]

The link is now a button under **Pipelines > Pipelines** and **Pipelines > Builds**.
There is no more **CI settings** menu.

This reverts commit 3e991230.

# Conflicts:
#	app/models/project.rb

The space between the [label] and the (link) caused it to be interpreted literally.

Borrowed from a user's comment:
https://gitlab.com/esr/reposurgeon/merge_requests/27#note_3158109

[ci skip]

[ci skip]

[ci skip]

Closes #12497

* Remove references to enabling CI since it it will be deprecated
* Revert changes in yaml/README.md, refine it in a separate MR