- Move `SAST_DISABLE_BABEL` to analyzer-specific settings
- Move `SEARCH_MAX_DEPTH` to vulnerability filters

Resolve RSpec/EmptyLineAfterLetBlock Exceptions in QA

See merge request gitlab-org/gitlab!38611

Fix failure with PO translation linter when there are no translations

See merge request gitlab-org/gitlab!38788

Update Vulnerability::IssueLinks when moving Issues to new Project

See merge request gitlab-org/gitlab!38765

Merge branch '219818-replace-gl-deprecated-button-with-gl-button-in-ee-app-assets-javascripts-vue_shared' into 'master'

Replace GlDeprecatedButton in dismissal_comment_modal_footer.vue

Closes #219818

See merge request gitlab-org/gitlab!38074

Add copy for Jira issues integration to GitLab issues empty state

See merge request gitlab-org/gitlab!38586

Add ability to board list create service to create backlog list

See merge request gitlab-org/gitlab!38648

Partially revert "Optimise the external diff storage migration query"

See merge request gitlab-org/gitlab!38789

Graphql count and filter MRs by merged at

See merge request gitlab-org/gitlab!38584

Removes Configure ownership from Go style guides

See merge request gitlab-org/gitlab!38748

Merge branch '231372-sast-config-ui-page-basic-sast-wide-settings-wire-up-graphql-query-to-dynamic-form' into 'master'

Wire up GraphQL query to dynamic form

See merge request gitlab-org/gitlab!38318

Part of the [SAST Configuration UI][epic] feature, this adds a GraphQL
query to the SAST Configuration UI application, and feeds a transformed
copy of the response to the [`DynamicFields`][1] component in order to
render the form fields.

The usage of `DynamicFields` in this change is not ideal, but is only
written this way for now to demonstrate the data flow. This will be
improved in a related MR soon. Specifically, what's not ideal:

 - It currently mutates the fetched GraphQL response, rather than
   working with a copy of it.
 - It's not contained within a `form` element, and there's no way (yet)
   to _submit_ the form data.

Other changes include:

 - Replace Bootstrap utility class with one from GitLab UI.
 - Extract helper for populating data for the frontend.
 - Change subheading text to match latest design.
 - Move documentation link into subheading.
 - Add error state for app component.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/231372.

[epic]: https://gitlab.com/groups/gitlab-org/-/epics/3659
[1]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38162

Raise warning when job:rules can trigger multiple pipelines

See merge request gitlab-org/gitlab!38387

Add dependency path in dependency list

See merge request gitlab-org/gitlab!38570

This adds path to the existing dependency list location
if they are available

Wire backend provided URL in package history

Closes #232828

See merge request gitlab-org/gitlab!38787

Add Sidekiq worker context for project imports

See merge request gitlab-org/gitlab!38698

- Move the filter from ProductivityAnalytics
- Expose `merged_after` and `merged_before` arguments in GraphQL

To GitLab issues empty state

A warning will be raised when `workflow:rules` is not defined and
last of the `job:rules` uses `when:(anything but "never")` without
clause.

Reassign page to Enablement stage

See merge request gitlab-org/gitlab!38713

When the HTML todolist contained a string that had no translations this
method was producing an error as it tried to call `.include?` on a `nil`
object.

Fix this by checking for the presence of translations first.

Caused by: https://gitlab.com/gitlab-org/gitlab/-/issues/217933
Errors appearing in:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38772

- source component
- test
- mock data

Fix vulnerability history query path

Closes #233916

See merge request gitlab-org/gitlab!38790

Add guideline about resetting schema cache in migration docs

See merge request gitlab-org/gitlab!36015

If using ActiveRecord, there may be cases where the schema is changed
in a previous migration and is cached, resulting in weird behaviors if
using the column that was altered but not refreshed.

As per https://github.com/rails/rails/pull/24300#issuecomment-201321397,
reset_column_information should be used when using models in migrations.

Revert "Merge branch 'id-remove-lfs-check-ff' into 'master'"

See merge request gitlab-org/gitlab!38723

Fix external links errors

See merge request gitlab-org/gitlab!38507

https://about.gitlab.com/handbook/engineering/ux/technical-writing/#regularly-scheduled-tasks

Clean up design management `item_spec.js`

See merge request gitlab-org/gitlab!38472

Replace gl-text-black-normal with gl-text-body

See merge request gitlab-org/gitlab!35857

Better axis labels for burndown charts

See merge request gitlab-org/gitlab!38113

Also for burnup charts.
1. Set min of 1 day (as that is our bucket size)
1. Set min of 1 on the y-axis
1. Format dates in a more human-friendly way
1. Remove avg/max from chart legend

This solved one problem, but introduced another. Revert the functional
change while keeping the rearrangement of code to make future changes
easier.

Resolve "Allow setting a default role for Group SSO"

See merge request gitlab-org/gitlab!37801

This change allows setting a default role
for Group SSO