Part of this is caused by the removal of "changed"
and "staged" split.

**How come?**

When there was this split, it was acceptable to
see "what's changed compared to staged (or HEAD)".
Now that there is only "staged", when we open we
were unfortunately comparing the "staged" content
against intself...

Fix flaky Jenkins e2e spec javascript error

See merge request gitlab-org/gitlab!29494

Migrate CE & EE controller specs to consider admin mode

See merge request gitlab-org/gitlab!28770

Update QA variables spec

See merge request gitlab-org/gitlab!25924

Create project label for jira imported issues

See merge request gitlab-org/gitlab!29246

Enable store_merge_request_line_metrics FF

See merge request gitlab-org/gitlab!29483

Use NOT VALID to enforce a NOT NULL constraint on file_store to ci_job_artifacts, lsf_objects and uploads tables

See merge request gitlab-org/gitlab!28946

Merge branch '213799-optimize-usage_activity_by_stage-projects_with_repositories_enabled' into 'master'

Optimize projects with repositories enabled

See merge request gitlab-org/gitlab!29117

Moved GraphQL-related data from Snippet Show into a mixin

See merge request gitlab-org/gitlab!29444

Replace deprecated GlLoadingIcon sizes

See merge request gitlab-org/gitlab!29417

Merge branch '30146-let-s-encrypt-integration-doesn-t-scale-and-does-not-give-any-feedback-to-user-on-errors-2' into 'master'

Add email notifications for failed Let's Encrypt integration

See merge request gitlab-org/gitlab!28581

The file.object_store is set during `uploader.store!`
which happens after object is inserted/updated. This
tries to mimic the default values in ObjectStorage
concern.

When adding a constraint to a table, we can optionally include
NOT VALID. This tells Postgres that it doesn’t need to enforce
the constraint on existing records in the table. At least not
immediately. This constraint will be enforced for any updates
and subsequent insertions. Thus, we can immediately enforce
the constraint while giving ourselves time to clean up any
existing records that conflict with the constraint.

Adds an index as well as start/finish times to optimize the counter

Create label when import starts and set label title based on
imported jira project key and previous import counts for the
same jira project.

Add rate limit  to issue creation

Closes #55241

See merge request gitlab-org/gitlab!28129

Updated page object and relative
spec to ensure E2E is working
like it should.

Fetch annotations for monitoring dashboard

See merge request gitlab-org/gitlab!28394

Monitoring dashboard fetches all annotations
associated to it. This change is behind
metrics_dashboard_annotations feature flag until
the backend is implemented

Create a table for storing diff note positions

See merge request gitlab-org/gitlab!28113

Create cop for AR count/each to size/each in HAML file

See merge request gitlab-org/gitlab!28883

Remove feature flag for dropping duplicate jobs

See merge request gitlab-org/gitlab!29116

by retrying on exception
Also remove quarantine tag

The same GraphQL props/data/query will be used for the Edit
application as well

Default schema for snippet

Add management_project_id to group and project cluster creation

See merge request gitlab-org/gitlab!28289

fix: Publish toolbar dissappears when submitting empty content

See merge request gitlab-org/gitlab!29410

Increase times for the merge request widget polling

Closes #210377

See merge request gitlab-org/gitlab!29318

We'll extract there notes' position and original
position

Docs: Forked and parent project visibility for MRs

Closes gitlab-com/support/docs#87

See merge request gitlab-org/gitlab!28256

Add autostop check to folder table

See merge request gitlab-org/gitlab!28937

Update dependency @sourcegraph/code-host-integration to v0.0.36

See merge request gitlab-org/gitlab!29445

Docs: update reference-style links to standard

See merge request gitlab-org/gitlab!29201

Truncate JUnit test report test case name

See merge request gitlab-org/gitlab!27144

See GlLoadingIcon component
in @gitlab/ui for size mappings.

Remove `error` from UI

See merge request gitlab-org/gitlab!29281

When a user submits empty content in the Static Site Editor,
the publish toolbar dissappears because the originalContent
property becomes empty. The isContentLoaded property depends
on the originalContent property to determine if there is
content to display.

This change decouples detecting that content is loaded from
detecting changes in the content