Remove VulnerableProjectsController(s) and related logic

See merge request gitlab-org/gitlab!40179

Fix incorrect project path warning after failed project path rename

See merge request gitlab-org/gitlab!40422

Create `IssuableSeverity` model to store a severity level for Incidents

Closes #238562

See merge request gitlab-org/gitlab!40272

Quarantine all monitor specs

See merge request gitlab-org/gitlab!40498

Increase clickable area of toggle_button.vue

Closes #235965

See merge request gitlab-org/gitlab!40231

Adjust some specs to Ruby 2.7

See merge request gitlab-org/gitlab!40490

Make web IDE the preferred editor for .gitlab-ci.yml

See merge request gitlab-org/gitlab!39508

Add alert for using the ide
for editing .gitlab-ci.yml
files. Also edit setup project
button to open .gitlab-ci.yml.

Epic labeling for confidential epics

Closes #229768

See merge request gitlab-org/gitlab!39794

As we started using GraphQL for letter grades information, these
controllers became obsolote therefore we are removing them from the
codebase.

Refactor storage of import_status

See merge request gitlab-org/gitlab!40160

Refactor store to maintain importStatus as part of importedProject
It reflects real state on backend side

Revert "Merge branch '227114_populate_resolved_on_default_branch_column_for_existing_vulnerabilities' into 'master'"

See merge request gitlab-org/gitlab!40494

Merge branch '241138-remove-the-ci_expand_names_for_cross_pipeline_artifacts-in-gitlab-ci-features' into 'master'

Remove FF helper method ci_expand_names_for_cross_pipeline_artifacts?

Closes #241138

See merge request gitlab-org/gitlab!40385

Closure policy for inactive bugs

See merge request gitlab-org/gitlab!39693

Refactor(VSA): Separate query and state management

See merge request gitlab-org/gitlab!39603

Separate filter bar store and actions from app
store and actions to prepare for a general
analytics filter bar solution

Use url-sync component instead of mixin to
separate concerns between base and filter-bar

Rename service model scopes

See merge request gitlab-org/gitlab!40418

Create security_on_demand_scans_scanner_profiles feature flag

See merge request gitlab-org/gitlab!39250

Update merge request diff files_count cache when removing diffs

Closes #240921

See merge request gitlab-org/gitlab!40384

Move Pages directory in Sidekiq when renaming a project

See merge request gitlab-org/gitlab!40087

Specify custom path for Vault auth method

Closes #241130

See merge request gitlab-org/gitlab!40366

Fixed batch comments styles not loading in FOSS

Closes #240235

See merge request gitlab-org/gitlab!40479

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/240235

Override the parallel diff lines property with new data

See merge request gitlab-org/gitlab!40131

Doing it this way allows us to:
1. Allow all existing code to work without changing a lot
2. Migrate all the code away from this property
once this feature has been fully rolled out

https://gitlab.com/gitlab-org/gitlab/-/issues/236143

Update factory doc with common change information

See merge request gitlab-org/gitlab!40308

Revert "Merge branch '227114_populate_resolved_on_default_branch_column_for_existing_vulnerabilities' into 'master'"

This reverts commit 00452a5e, reversing
changes made to 8b7b5a53.

This reverts commit 7eac2cf6.

The files_count cache column was created with the assumption that the
number of files never changes throughout the life of a diff. However,
we have discovered the DeleteDiffFilesWorker, which removes them (and
sets the state of the diff to :without_files) in some limited cases.

This MR updates the cache columns (both commits_count and files_count)
so they will be re-recorded on every update. Since updates are rare,
the additional cost of this should be very low.

When creating confidential epics/ issues in epic tree
show better labeling

Improve error message for job configs that fail to match an entry

See merge request gitlab-org/gitlab!40120

There's no practical difference between two, but any_args
accepts no_args as an options as well

This is behind the async_pages_move_project_rename feature flag. When
it's enabled and a project is renamed, we do not move the Pages
directory in Puma - instead, we schedule a Sidekiq job to perform the
move.

We already weren't checking the return value of
`Gitlab::PagesTransfer#rename_project`, so this shouldn't introduce any
failure cases that weren't there already.

Fix: already initialized constant warnings for HTTPError

Closes #239380

See merge request gitlab-org/gitlab!40142