Based on the
https://gitlab.com/gitlab-org/gitlab-ee/issues/8429
issue for the required pipeline configuration setting.

All code blocks should be surrounded by blank lines

Doc for "Allow a template in a namespace which is out of the
hierarchy of the Group owning the template"

Hard tabs do not follow general markdown guidelines
are were removed from the few docs that used them

GitLab uses a kubernetes service account to perform deployments. For
serverless deployments to work as expected with externally created
clusters with their own knative installations (e.g. via Cloud Run), this
account requires additional permissions in the serving.knative.dev API
group.

We fetch the users from Phabricator based on their Phabricator ID. If
a user with the same username exists and is a member of the project,
we set them as assignee or author.

When a user is applicable, we also cache it in Redis so we don't have
to perform the request again for the same phid.

The documentation is updated to include details on the new
limitations and rules to naming NPM packages. A note is included
on how naming collisions are handled.

The configuration is currently only specified in CI, by moving it into
`.mdlrc` we get immediate feedback locally in supported editors.

To ensure `mdl` is available it's also added to the `Gemfile`, though
CI will still use the version installed in the `gitlab-docs-lint` image.

This updates redirected links in integration, update, user
and workflow dirs. Should now link to final URLs to avoid
redirect hops

Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.

This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.

See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800

Current screenshots are from an older version of Jira and GitLab.

Change assorted absolute links to ce and ee docs
to relative links

Currently, we label items to be done as "Todo." This is grammatically
incorrect and (therefore) confusing—especially to our Spanish-speaking
users for whom "todo" has a specific and unrelated meaning.

We should use "To Do" and always use it as singular (not "To Dos").

Updates to wording in a few places per MR (ee) discussion

Updating locale/gitlab.pot

Updates to wording in a few places per MR (ee) discussion

Updating locale/gitlab.pot

Some general code has been added/removed in EE version
which needs to be backported in CE

Change csv import section to bullet list, add back missing
bulk import section, and resolve minor issues raised in
https://gitlab.com/gitlab-org/gitlab-ce/issues/64102

After review, heading was changed and links to
it needed to be updated, and minor tweaks to
the issues docs such as note formatting

Add backticks around square brackets, or fix links, as necessary.

Includes changes to the Vue container registry component to support
the display of an empty message and error message when invalid
characters are found in the group, project or branch name.

repositories/index.html.haml has been changed to remove the content
and place into Vue component.

- JupyterHub must not be available (installed or updated)

Linting rule not enabled for now
because tooling produces false
positives.

This reverts commit 092542d2fa5c036e4fc01ba3185f1dc0e9ddbebb.

Included a stray file