Remove newIssue function logic from list model

See merge request gitlab-org/gitlab!32244

Remove addAssignees logic from issues model

See merge request gitlab-org/gitlab!32231

Remove LSIF API endpoints which aren't used

See merge request gitlab-org/gitlab!32325

Add Kubernetes::NetworkPolicy#autodevops?

See merge request gitlab-org/gitlab!32715

Create operations_feature_flags_issues Table

See merge request gitlab-org/gitlab!32876

For linking feature flags and issues

Fix Merge Request Note Label URLs

See merge request gitlab-org/gitlab!30428

Standardize template names

See merge request gitlab-org/gitlab!32612

Infer merge request in Discussions::ResolveService

See merge request gitlab-org/gitlab!32932

Docs - how to get license details via Rails console

See merge request gitlab-org/gitlab!33123

Merge branch '219193-foss-job-failure-with-unintialized-constant-uninitialized-constant-gitlab-throttle-in-spec' into 'master'

Remove `/config/initializers/rack_attack.rb` from `.gitignore`

Closes #219193

See merge request gitlab-org/gitlab!33128

We used them for the first code intelligence iteration
Now we don't need them, so we can remove

Add docs for the PostHog cluster application

See merge request gitlab-org/gitlab!29152

This change allows Discussions::ResolveService to infer the related
Merge Request without the params[:merge_request] being present.

Previously the param was expected to be passed and the service would
error if it were not present.

This change is being made for two reasons:

1) Discussions can be associated with Designs, which have no
relationship with Merge Requests. In order to be able to use this
service to resolve Discussions on Designs, we need to make this service
able to treat the param as optional.

2) This service is to be called from within the GraphQL API. It
shouldn't be the API's responsibility to find the related Merge Request
and pass it to the service, but instead the service should be
responsible for making sure the right services are called after
resolving Discussions on Merge Requests.

The params[:merge_request] has been kept as an optimisation for existing
code that has fetched the Merge Request already before calling the
service (this won't be the case for the GraphQL API).

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

Added AWS credentials for Docker credential helper

See merge request gitlab-org/gitlab!30938

Docs: Add no transfer note

See merge request gitlab-org/gitlab!33086

Add instructions for masking credentials

See merge request gitlab-org/gitlab!32948

Add metadata to Plan pages

See merge request gitlab-org/gitlab!32682

Resolve "Avoid N+1 queries on project search"

See merge request gitlab-org/gitlab!30346

Follow-up propagate integrations service

See merge request gitlab-org/gitlab!32748

Update application_settings schema on db/structure

See merge request gitlab-org/gitlab!33091

Allow manual rollout jobs to fail

See merge request gitlab-org/gitlab!32865

Add quick actions for iterations in issues

Closes #196795

See merge request gitlab-org/gitlab!32904

Updates alert status enum values

See merge request gitlab-org/gitlab!32697

Remove prepend-left-4 CSS class

See merge request gitlab-org/gitlab!33002

GraphQL: hasPreviousPage and hasNextPage not working consistently

Closes #218340

See merge request gitlab-org/gitlab!32476

for stable/keyset cursor pagination

When we migrated to rules syntax, we missed the fact that these jobs
were previously allowed to fail, see

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

Add suggested limit of 25 words per sentence

See merge request gitlab-org/gitlab!30743

This removes the prepend-left-4
CSS class and replaces it for the
GitLab-UI equivalent gl-ml-2 utility class

* Updates sorting vars in FE

Docs for VSA cycle time and lead time

Closes #217997

See merge request gitlab-org/gitlab!32359