make `karma -f` work again

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

Update `gitlab` chart docs for GA

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

Port of tc-api-fork-owners to EE

Closes gitlab-ce#40550

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

Resolve "All Gitlab branches listed in Jira task in Development section"

Closes #6752

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

Resolve "Follow up - Protected Environments: Use limited count approach"

Closes #7175

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

[Rails5] Fix project's path check

Closes #7081

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

A forked project stores its LFS objects in the `forked_from_project`.
So the LFS objects become inaccessible, and therefore delete them from
the database so they'll get cleaned up.

To be refactored when implementing
https://gitlab.com/gitlab-org/gitlab-ce/issues/39769

Before this change only GitLab admins where allowed to set up forking
relation through the API. This changes that so project owners can
do this too.

Closes gitlab-org/gitlab-ce#40550.

Add weight to issue hook

Closes #6274

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

Docs update ha aws diagram

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

CE upstream - 2018-08-19 06:21 UTC

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

When importing a project, after clicking 'Create Project' button, user is
redirected either to to the project's import page or project's show page
depending whether import is still in progress.

The difference in behavior is probably caused by `test_after_commit`
which is now included in Rails 5.

Jira needs to be given a bare domain (no path) for its configuration,
otherwise it confuses itself and does not use the proper API endpoints.
This was the reason why we always say requests like `/-/jira/pulls`
before (it uses whatever path is given always)

Remove Gemnasium service

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

Rails5: fix mysql milliseconds problem in project registry spec

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

Update README.md

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

EE: Refactor AutocompleteController

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

Fix incorrect syntax on `code_quality` CI step

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

formatting fix

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

Trivial fix: variable names in error message

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

fix typo

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

Change approvals_missing to approvals_left.

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

Fix `warn_user_is_not_gitlab`

Closes #5896

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

Actually create the job in the `test` stage

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

Documentation: Fix API doc link from MR approval to MR acceptance

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

Rails5: Fix audit event spec

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

This refactors the AutocompleteController according to the guidelines
and boundaries discussed in
https://gitlab.com/gitlab-org/gitlab-ce/issues/49653. Specifically,
ActiveRecord logic is moved to different finders, which are then used in
the controller. View logic in turn is moved to presenters, instead of
directly using ActiveRecord's "to_json" method.

The finder MoveToProjectFinder is also adjusted according to the
abstraction guidelines and boundaries, resulting in a much more simple
finder.

By using finders (and other abstractions) more actively, we can push a
lot of logic out of the controller. We also remove the need for various
"before_action" hooks, though this could be achieved without using
finders as well.

The various finders related to AutcompleteController have also been
moved into a namespace. This removes the need for calling everything
"AutocompleteSmurfFinder", instead you can use
"Autocomplete::SmurfFinder".

Rails5 fix duplicate gpg signature in path lock spec

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

Rails5: fix mysql milliseconds problem in project_spec

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

Rails5: fix mysql milliseconds problem in project_import_state_spec

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