A user could have multiple identities with `provider: 'group_saml'`, one
for each GitLab.com group to which they belong. The change in
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14045 would only
update one of these identities via `find_or_create_by`. To fix this,
also account for `saml_provider_id` if it's available.

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/12303

Resolve "Docs feedback: revise operations dashboard"

Closes #60697

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

Add code comments development guide

Closes #63132

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

(CE Port) Set project path on localStorage during onboarding

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

Set project path on localStorage during onboarding

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

- bind events on new project page

Resolve "Follow-up from "Use scoped routes for labels and milestones""

Closes #63177

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

Remove baseEndpoint from search dropdwon

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

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

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

Move vuex action helper spec to Jest

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

This is largely a straight-forward copy of the Karma spec, with the
usual Karma->Jest necessary changes.

This also fixes a bug in the implementation that was causing the tests
to fail, when run on Jest/node, whereby actions that return rejected
promises would always fail the given test. This was due to those
rejections not being caught in the same call stack in which they were
created.

Clarify that this.something is not available in Jest (docs)

Closes #24809

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

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Resolve "Track onboarding events in Snowplow"

Closes #11409

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

- Add nav_source param to skipUrl for tracking

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

Copy issue boards list model from CE

Closes #12365

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

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>
```