There are no visual changes as a result of this
commit.

Improves user flow when installing the GitLab for Jira
app.

Moves the file to a page specific bundle and includes
it on the relevant pages. Also combines
experience_level.scss into the new page bundle.

Since the styles in diff.scss does not relate to a specific page,
and is used in many parts of the site, it is more relevant to have
it placed in the framework directory.

Moves the file to a page specific bundle and includes it
on the relevant page. Also combines error_tracking_list.scss
into the new page bundle.

And into a page specific bundle which is imported in the
merge requests page.

Moves the file to a page specific bundle and includes it
on the relevant pages.

In this change we wrap the CSS of the pipeline table that only appears
in 4 pages, inside a `[data-page]` selector to scope where it is used.

Additionally some unused/abandoned styles are removed.

When a user attempts to destroy a Web hook, the database will attempt to
delete all the associated Web hook logs. However, as we have seen in
https://gitlab.com/gitlab-org/gitlab/-/issues/21940, the table may be
too bloated or the number of rows too large that this deletion can time
out due to a 15-second statement timeout.

We rectify this situation by deleting these logs in batches of 1000
outside of a transaction. That should be acceptable since old logs get
pruned periodically anyway, and when a Web hook is destroyed it's more
important that the destruction makes progress and eventually removes the
hook.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/21940

And into a page specific bundle which is imported in the
dev ops reports page.

Previously, an integration with the webpack-rails gem required
juggling and consolidating two separate webpack configurations
the one used by the rails gem and the one defined in gitlab.yml

This update moves all webpack integration settings into the
gitlab.yml file and updates references such that they don't need
to be overridden in confusing ways.

Make environments CSS a separate bundle
Use CSS variables instead on SCSS ones

Extract "issues_list.scss" into its own under page_bundles.

Move .issue_list into "page_bundles/issues_list.scss"
from "pages/issues.scss"

Merge "page_bundles/issues.css" which contained stylings
,.user-can-drag and .is-ghost, only relevant to issues list
into "page_bundles/issues_list.scss".
(boards and epic duplicate .user-can-drag and .is-ghost
in their own scss).

Use gray-10 over gray-light as background color
for displaying issue list when in manual ordering mode.

Also moves color variables to css variables for
dark mode support

Removed the cropper css line application
Apply 3 suggestion(s) to 3 file(s)
Fix for GL Crop dataset and Linter error on profiles

In order to reduce the size of files loaded in all page, this change
moves most of the CSS used in the display of a single pipeline, to
a page bundle, to be displayed independently.

When we extract page specific CSS, they sometimes overwrite our utility
classes and and force us to use important! utility classes. [0]

In order to make our utilities take precendence, we split them off, so
we can import them later. Note that we have to do it once for light mode
and dark mode.

[0]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42795#note_415620902

sprocket-rails adds some precompile assets we actually do not need.

It copies all _non_ js and CSS files from the app/assets/ older.

In our case this copies for example: Vue, Markdown and Graphql, which we
do not need for production.

We remove this default behavior and then reimplement it in order to
consider ee/ as well and remove those other files we do not need.

For reference: https://github.com/rails/sprockets-rails/blob/v3.2.1/lib/sprockets/railtie.rb#L84-L87

In order to show how one would extract a page specific CSS bundle with a
separate EE version, we have done the exercise for Value Stream
Analytics. Caveat: Some colors have been changed.

Currently `app/assets/` is always taken before `ee/app/assets`, because
it is prepended by sprocket-rails. By creating our own initializer we
can insure that `ee/app/assets` takes precedence.

Make ce boards.scss page specific
Copy across epics.scss drag & drop CSS
Create page specific issues.scss for drag & drop style

This change incorporates the methods needed to read the webpack
manifest file from the deprecated webpack-rails gem into gitlab
itself. We will now be able to maintain it ourselves and modify
it to do things like listen on unix file sockets for dev-server

Make CE milestone.scss page specific
Import on group and project list milestones list
Import on group and project milestone page

`ruby-graphql` supports

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27464 added support
for a custom `deprecated` keyword for `field` to allow us to specify the
milestone that a field was deprecated in a structured way.

Enum values are also able to be deprecated. This change adds support for
enum values.

Also see: https://gitlab.com/gitlab-org/gitlab/-/issues/199952

This moves all themes for the navbar themes to their own file
Inlines them for startup css or loads them
On theme selection we load all themes

This moves the following things to Core:
- Jira DVCS Connector
- Jira Connect App
- Usage ping for those two features

and removes any license check related to them.
Co-authored-by: Craig Norris <cnorris@gitlab.com>

Instead of using globbing and because we want to move these page
specific styles to the appropriate pages, we move the imports to a new
file.

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38052

- Serve fontawesome fonts
via sprockets

Notifications generate this deprecation error:

```
DEPRECATION WARNING: Sending mail with DeliveryJob and
Parameterized::DeliveryJob is deprecated and will be removed in Rails
6.1. Please use MailDeliveryJob instead. (called from new_project_member
at /builds/gitlab-org/gitlab/app/services/notification_service.rb:360)
```

This was introduced in Rails: https://github.com/rails/rails/pull/34591.

To migrate, we simply need to set the Rails configuration to use
`MailDeliveryJob` instead of `DeliveryJob` and update the code to
reflect that.

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

This is going to be used early when computing Runtime.max_threads so
we can't use gitlab.yml to store these.

This reverts merge request !34291

Basically invert color scales, plus a bit of palette
reduction to make things easier

Mark color vars in variables as !default, then they can
be overridden by importing a theme first. Export separate
application_dark.css file

This reverts merge request !33943

Gitlab::Runtime.multi_threaded? now requires access to Gitlab.config
which isn't available early on in these initializers.

We don't really need this setting anyway because this just wraps the app
in a mutex so that it can only be called by one thread at a time.

We're already running Puma by default so we're confident that our
application works without this mutex.

Adds an option in gitlab.yml to run ActionCable in in-app mode

Connection pool settings are also adjusted to account for the extra
threads

In production mode, eager loading is enabled, and Devise is configured
by default to reload routes before eager loading. However, in
`config/application.rb` we also attempted to reload routes, which added
another 5-10 seconds of delay. In development mode, eager loading is
disabled, so we don't see this extra overhead.

To speed boot times, we only reload the routes if eager loading is
disabled.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/213992

Currently, IP spoofing attacks result in a 500 response, which counts
towards our error budget. Since they're caused by the properties of the
client request, it's appropriate to convert them into 400 errors.

We don't need to be too worried about the format of this response, as
only malicious users will see it.