Remove FF ci_parent_child_pipeline

See merge request gitlab-org/gitlab!30601

Cop to restrict methods within with_lock_retries

See merge request gitlab-org/gitlab!30838

Fix db:check-schema in forks and shallow clones

Closes #216214

See merge request gitlab-org/gitlab!30950

I changed merge into merging

See merge request gitlab-org/gitlab!30437

Fix assigning issues to users for Jira import

See merge request gitlab-org/gitlab!30967

Prevent Seat Link Sync when license has no expiration

Closes #215354

See merge request gitlab-org/gitlab!30874

Remove FF ci_doom_build

See merge request gitlab-org/gitlab!30595

Remove FF ci_set_project_default_git_depth

See merge request gitlab-org/gitlab!30589

Add tests for passing nil values in epics and packages

See merge request gitlab-org/gitlab!30949

Remove feature flag :webide_dark_theme

See merge request gitlab-org/gitlab!30916

Add @kerrizor --> /ee/lib/gitlab/code_owners/

See merge request gitlab-org/gitlab!30939

- Eliminates WithLockRetriesWithoutDdlTransaction cop.
- Introduce a new cop to restrict methods within
`with_lock_retries`

The `regenerate-schema` script attempts to find the merge base between
the source and branch SHA to determine the right `db/structure.sql` to
apply the migrations in the merge request. However, to get the merge
base, we need the target SHA and the history between the source and
target SHAs. Instead of downloading it via a curl request, we fetch the
target branch and check out the `db/structure.sql` from there.

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

Geo: retrieve api endpoint should return correct file content

Closes #213829

See merge request gitlab-org/gitlab!30686

Repository Analytics: Add title to page

See merge request gitlab-org/gitlab!30855

Contribution Analytics: Add title to page

See merge request gitlab-org/gitlab!30842

Add status dropdown to alert list view

See merge request gitlab-org/gitlab!30434

Refactor related branches controller action and view template

See merge request gitlab-org/gitlab!30314

Fix showing New requirement button to unauthenticated user

Closes #214991

See merge request gitlab-org/gitlab!30085

Move Design Management models to FOSS

See merge request gitlab-org/gitlab!30015

Gitlab/Json autocorrects in /ee

See merge request gitlab-org/gitlab!30625

Add initial statistics for WAF installations

See merge request gitlab-org/gitlab!28331

docs: Fixed small typo

See merge request gitlab-org/gitlab!30953

Remove unused cluster configuration workers

Closes #27481

See merge request gitlab-org/gitlab!30695

Quarantine pull mirroring spec while we investigate the issue

See merge request gitlab-org/gitlab!30954

This change is part of
https://gitlab.com/gitlab-org/gitlab/-/issues/212566 to move all Design
Management code to FOSS.

This MR moves:

- Models
- Factories
- Design repository-related code

The repository-related code has been included because the models and
model specs rely on design repositories to be working.

Decouple partial clone config

See merge request gitlab-org/gitlab!30354

Previously partial clone configs is coupled with receive_max_input_size
check. This make sense when you think of partial clone as a replacement
for Git LFS but in truth, the 2 features are separated and should not be
 decoupled.

In self-managing instances, `receive_max_input_size` could be set to 0
while users could still wish to have partial clone feature enabled.

References:
- [Original discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16850#note_313323533)
- [Tracking issue](https://gitlab.com/gitlab-org/gitlab/-/issues/212926)

Configure connection pools for ActionCable

See merge request gitlab-org/gitlab!29725

Raise Internal Server Error on 500 in `api_get_from`

See merge request gitlab-org/gitlab!30844

So that a resource should not treat it as ResourceNotFoundError and
try to create a new resource.

Use ActionCable's worker pool size to determine connection pool size

In https://gitlab.com/gitlab-org/gitlab/-/issues/215936, we found that
upgrading to Grape v1.3.2 caused a regression in our QA suite because
passing a `nil` value for an Array type would be passed in as a `nil`
value instead of being coerced to an empty Array. We had to revert the
upgrade as a result. To ensure that `nil` values are handled properly on
the backend, add tests for this.

Fix failing spec in ee/spec/features/boards/sidebar_spec.rb

Closes #216364

See merge request gitlab-org/gitlab!30945