Extract code owners from a CODEOWNERS file

Closes #6961

See merge request gitlab-org/gitlab-ee!6916

EE port for 29398 support kubernetes rbac for gitlab managed apps

See merge request gitlab-org/gitlab-ee!6946

Fix usage statistics typo documentation

See merge request gitlab-org/gitlab-ee!7265

CE upstream - 2018-09-05 21:23 UTC

Closes #6136

See merge request gitlab-org/gitlab-ee!7259

Jira DVCS docs - Call out differences between 11.3 and before

Closes #7400

See merge request gitlab-org/gitlab-ee!7255

Update user markdown documentation for CommonMark

See merge request gitlab-org/gitlab-ee!7241

port "Improve project overview UI" to EE

See merge request gitlab-org/gitlab-ee!6844

In a file called `CODEOWNERS` in the root of a repository, in the
`docs/`-folder or in the `.gitlab/` folder it is possible to define
users that are 'owners' for specific code paths.

A pattern can be defined on each line in the same way as it would in a
`.gitignore` file. After that, one or more users can be specified
using their username (using the `@username` format) or email address
linked to their account. Comments can be preceded with a `#`. If a
filename starts with `#` this can be escaped using `/#`.

For example:

    # All files in the `docs/` directory should be reviewed by a
    # technical writer:
    docs/* @jane @joe

    # Ruby files should be reviewed by a backend maintainer:
    *.rb alice@development.gitlab.org

The code owners will be displayed when viewing a blob, if a user for
the username/email cannot be found, nothing will be shown.

When multiple patterns match the blob being viewed, the last entry
will be used.

Expand instance-level templates to cover .gitlab-ci.yml, .gitignore and Dockerfile

Closes #5306

See merge request gitlab-org/gitlab-ee!7000

# Conflicts:
#	app/views/groups/labels/index.html.haml
#	doc/ci/yaml/README.md
#	lib/gitlab/ci/config.rb

[ci skip]

Add route information to lograge structured logging for API logs

Closes #50993

See merge request gitlab-org/gitlab-ce!21487

Fix documentation on upgrading when using a Helm chart

See merge request gitlab-org/gitlab-ce!21539

Fix an error in docs about fetching artifacts using API

Closes gitlab-ce#50883

See merge request gitlab-org/gitlab-ee!7244

Add support for advanced CI/CD config extension with `extends:`

Closes gitlab-ee#6136

See merge request gitlab-org/gitlab-ce!21243

Add support for advanced CI/CD config extension / EE

See merge request gitlab-org/gitlab-ee!7250

Fix app/views/projects/settings/repository/show.html.haml

See merge request gitlab-org/gitlab-ee!7253

Merge branch 'ee-45938-postgres-timeout-when-counting-number-of-ci-builds-for-usage-ping' into 'master'

Resolve "Postgres timeout when counting number of CI builds for usage ping"

See merge request gitlab-org/gitlab-ee!7251

Fix multipart error on rails reload

See merge request gitlab-org/gitlab-ce!21540

remove comma

See merge request gitlab-org/gitlab-ce!21536

Merge branch '45938-postgres-timeout-when-counting-number-of-ci-builds-for-usage-ping' into 'master'

Resolve "Postgres timeout when counting number of CI builds for usage ping"

Closes #45938

See merge request gitlab-org/gitlab-ce!21523

Document that when updating using a Helm chart 'helm repo update' needs to be run before the 'helm upgrade ...' command.  

then each commit or push triggers your CI pipeline.