Clarify that Jest does not use Webpack (docs)

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

Upgrade Gitaly to v1.49.0

Closes gitaly#1738

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

The setup was wrong, and due to Gitaly being a bit more strict it had to
match up. The test is now accurate and passing again.

Silence backup warnings when CRON=1 in use

Closes #63703

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

Mention what tools are not supported in Dependency Scanning

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

CE backport: Resolve "Make "Create an issue" default for Incident Management"

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

This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.

Prevent EE backport migrations from running if CE is not migrated

Closes #63612

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

Improve Review Apps cleanup when previous deployment failed by only issuing an `helm delete` command

Closes #63639 and #62161

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

If CRON=1 is in use, we shouldn't generate any output or admins may be
notified via e-mail about unnecessary warnings.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63703

If a user upgraded to any GitLab 11.x EE version but switched
back to CE, it's possible the state of the EE tables are not
in the right state for the EE backport migration to work properly.
In particular, there were three tables that had trouble:

* epics
* geo_event_log
* vulnerability_feedback

The EE backport migration would fail while trying to add foreign key
constraints because a key didn't exist in the table. This happens
because any EE migration that add or removed columns between v11.0.0 and
v11.11.3 are not guaranteed to be applied in an CE installation. The EE
backport schema does not individually backport these migrations.

We now check if certain columns are present to determine whether
the backport migration is in the proper state. CE users are required
to upgrade to v11.11.3 EE if they ever installed EE previously before
they can go back to v12.x CE.

Tested via:

```
git checkout -f v11.0.0-ee
bundle exec rake db:reset
git checkout .; git checkout -f v11.11.3
bundle exec rake db:migrate
git checkout .; git checkout -f v12.0.0
bundle exec rake db:migrate
<failure happens>
```

Keep empty folders in the tree list

Closes #60860

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

Merge branch '62735-for-stable-branches-build-cng-images-from-corresponding-stable-branches-in-cng-mirror-project' into 'master'

Pass branch name to the CNG pipeline for stable branches

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

Update GitLab Runner Helm Chart to 0.6.0/12.0.0

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

When removing the last file from a folder in WebIDE, do not remove the
folder from the view. We keep those to give users possibility to
re-upload files to the same folders.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60860

Allow autocompleting labels using colons and spaces

Closes #63343 and #56510

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

The `:` key will no longer exit out of the autocomplete dialog,
allowing auto-completion of labels with colons in them.

Add gem size information to metrics.txt in memory CI artifacts

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

Use project depended feature flag for pages ssl and get certificates only for enabled domains

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

Refactor AfterCommitQueue.inside_transaction?

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

This is a small change to move AfterCommitQueue.inside_transaction?
to Gitlab::Database.inside_transaction? Since this change is required
by different changes which may not arrive in sequence, it's easier
to extract this change out on it's own.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Fix reports jobs timing out because of cache

Closes gitlab-ee#12021, #60879, and gitlab-ee#11303

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

Note: This commit relies on
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26801
which brings support to multiple extends.

While `cache: {}` can disable a cache being set globally, it doesn't
work with extends, which will perform a reverse deep merge based on the
keys.

The cache defined in the base `.default-cache` job
won't be disabled in the report jobs.

As a side effect, the `code_quality`, `sast`, and `dependency_scanning`
jobs are running on a larger code base than expected, leading to
timeouts.

fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/11303
fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/60879
fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/12021

Also add ::Gitlab::LetsEncrypt.enabled? shortcut
and simplify it a lot

Edit resource creation text

Closes #63643

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

Limit time tracking units to hours

Closes #30355

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

Vue-i18n: autofix for app/assets/javascripts/issue_show directory

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

i18n linting for .vue files under the
app/assets/javascripts/issue_show directory

Upgrade axios to 0.19.0

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

Vue-i18n: autofix for app/assets/javascripts/monitoring directory

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

Exclude docs-only branches from job

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

Add Markdown linting and one rule

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

Also adds and one linting rule
and makes project conform to it.