delta/gitlab/gitlab-ce.git/changelogs, branch docs-pages-force-https

Merge branch 'require-pipeline-when-enabling-only-allow-merge-if-pipeline-succeeds' into 'master'

2019-06-25T15:48:39+00:00

Pipeline must be present if "Pipeline must succeed" is set

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

Fix broken worktree test

2019-06-25T14:45:51+00:00

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.

Merge branch 'sh-quiet-backup-secrets-log' into 'master'

2019-06-25T14:32:19+00:00

Silence backup warnings when CRON=1 in use

Closes #63703

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

Merge branch 'sh-recover-ee-schema-backport-migration-failure' into 'master'

2019-06-25T14:03:54+00:00

Prevent EE backport migrations from running if CE is not migrated

Closes #63612

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

Silence backup warnings when CRON=1 in use

2019-06-25T13:30:51+00:00

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

Prevent EE backport migrations from running if CE is not migrated

2019-06-25T12:42:10+00:00

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

```

Merge branch '60860-keep-empty-folders-in-tree' into 'master'

2019-06-25T11:42:03+00:00

Keep empty folders in the tree list

Closes #60860

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

Merge branch 'update-gitlab-runner-helm-chart-to-0-6-0' into 'master'

2019-06-25T10:50:55+00:00

Update GitLab Runner Helm Chart to 0.6.0/12.0.0

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

Keep empty folders in the tree list

2019-06-25T10:32:35+00:00

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 scoped labels

2019-06-25T10:19:29+00:00

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