This is the first step towards generating all utility classes with
tailwind. The idea behind this is the following:

Parse all utility classes being provided by @gitlab/ui into a JSON
object where each class is represented as something like this:

```
'.bg-gray-10': {
  'background-color': 'var(--gray-10, #fbfafd)',
},
```

We then let tailwind generate all the utilities and compare the class
definitions above with the class definitions in @gitlab/ui. They can
fall into four categories:

- exact matches: The tailwind generated class matches @gitlab/ui 1:1
- potential mismatches: The tailwind generated class mismatches
  significantly. This can be okay or we may need some adjustments to the
  tailwind config.
- hardcoded colors: Some of the utility classes have hard coded colors
  which the conversion script is not able to resolve to a CSS variable.
- safe to use legacy utils: These utils have no overlap with tailwind at
  all. The class names completely differ. This means we can feed the
  definitions above into tailwind, so that tailwind is able to generate
  the classes

As part of the conversion certain aspects are normalized, for example
colors like `#fbfafd` are normalized to `var(--gray-10, #fbfafd)`, but
only if the class name contains `gray-10`.

Furthermore we currently check-in two files that later will be
git-ignored:
1. config/helpers/tailwind/css_in_js.js – containing the css-in-js
   definitions for tailwind to generate the legacy utils with tailwind
2. config/helpers/tailwind/all_utilities.haml – containing a list of all
   utility classes, so that tailwind is able to generate _all utilities_
   and not just the used ones

This allows us to fine-tune what is being indexed.
Since GitLab is quite large, and since by default
even dependencies are indexed, resource use and
duration is currently high.

The script `./scripts/frontend/compile_css.mjs` compiles our SCSS style
code to CSS. It follows the same rules/settings that our sassc-rails gem
currently does (compiling the same files) while using dart sass and not
the deprecated C implementation.

Compiled CSS files will be placed in `app/assets/builds` where they can
be picked up by the `cssbundling` gem. The gem _needs_ runs the npm
script `build:css`.

We also mark `sass` as a production dependency so that our license
scanning picks up everything properly.

One more note, the current MR doesn't integrate with the Vite and
Webpack dev servers yet, this would be done in a second step.

For more context see the in-progess MR:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/140611



Co-Authored-By: Muhammed Ali <muhammed.ali@airtimerewards.com>

This reverts merge request !141582

https://github.com/golang/tools/blob/master/gopls/doc/workspace.md

Refactor yarn commands

This allows us to pass the port and whether vite_ruby is actually
enabled from the GDK to GitLab Rails and feature specs.

Addressing: https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/1894
Changelog: added

This reverts merge request !115469

Changelog: other

Part of https://gitlab.com/gitlab-org/frontend/rfcs/-/issues/106.

As part of https://gitlab.com/gitlab-org/gitlab/-/issues/389749 we want
HTTP requests from `Zoekt -> GitLab` to be authenticated. This MR adds
the ability to configure a `zoekt.username_file` and
`zoekt.password_file` (that default to `.gitlab_zoekt_username` and
`.gitlab_zoekt_password` respectively) in your `config/gitlab.yml` .
If present these files will be used to populate basic auth credentials
in the HTTP requests to Zoekt. We likely won't use this in GDK because
basic authentication relies on an nginx proxy in front of Zoekt (this is
configured in the helm chart in
https://gitlab.com/gitlab-org/cloud-native/charts/gitlab-zoekt/-/merge_requests/14).
The indexer and webserver we run in GDK don't actually support basic
auth but I've verified locally that these changes do indeed send the
credentials.

EE: true
Changelog: added

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

This change updates the pipeline settings to run a separate job for
RSpec tests tagged with click_house.

Gitaly removed it's gitaly-ruby configuration in
gitaly@e361ab48 (config: Remove ruby configuration, 2023-03-16). So we
also can remove writing that section to the configuration toml.

This adds a new internal API to create access token for Suggested
Reviewers. Suggested Reviewers is an Machine Learning enabled feature
that requires merge request data for build project-specific feature
sets. The access token is used by the CI pipeline to call GitLab public
GraphQL API to fetch merge requests.

This commit adds a new config file config/redis.yml which is meant to
eventually replace config/resque.yml, config/redis.shared_state.yml,
config/redis.cache.yml, config/redis.queues.yml, etc.

Nothing changes in how we resolve Redis configuration unless the
administrator opts in by creating a config/redis.yml file _and_
putting configuration data in it.

Changelog: other

This reverts merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105975

This adds a new internal API to create access token for Suggested
Reviewers. Suggested Reviewers is an Machine Learning enabled feature
that requires merge request data for build project-specific feature
sets. The access token is used by the CI pipeline to call GitLab public
GraphQL API to fetch merge requests.

This change was introduced in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/103881
but reverted https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105930
because it breaks the migration due to write permission error.

This reverts merge request !103881

This reverts merge request !105347

This reverts merge request !103083

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

I discovered in
https://gitlab.com/gitlab-org/gitlab/-/issues/371710#note_1075889990


that the variable wasn't set for this job, resulting in missing test
files to be run by the `rspec foss-impact` job, leading to potential
FOSS broken `master`.

Signed-off-by: Rémy Coutable <remy@rymai.me>

We switched to Lefthook for some time now.

Signed-off-by: Rémy Coutable <remy@rymai.me>

- Add headers and anchors for individual input
  and output files.

- See related documentation added in
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/84220

MR: https://gitlab.com/gitlab-org/gitlab/-/issues/360212

Rémy Coutable 创作于 3年前 ，Lin Jen-Shin 提交于 3年前

Signed-off-by: Rémy Coutable <remy@rymai.me>

This reverts commit aec8fc7a, reversing
changes made to ec9a1f48.

- This change aims to reduce the feedback time when resolving failed
  tests for a Merge Request
- The setup jobs will detect the previous test files associated with
  failed jobs in the test stage of the previous pipeline
- The test stage jobs will execute a rerun based on those detected
  test files

This reverts merge request !69053

- This change aims to reduce the feedback time when resolving failed
  tests for a Merge Request
- The setup jobs will detect the previous test files associated with
  failed jobs in the test stage of the previous pipeline
- The test stage jobs will execute a rerun based on those detected
  test files

The main sticking point was `config/README.md`, which went into a lot of
detail about each instance. It was quite easy to make a copy and paste
error, as some instances had default URLs and others didn't, some had
fallback instances and others didn't, etc.

This changes a number of things:

1. `config/README.md` now has a table for the Redis instances with a
   single list of instructions that apply to all instances.
2. There are now specs to ensure that each Redis instance has a default
   URL set when no Redis config at all is present.
3. Instances that use a fallback instance for config will automatically
   use the default URL of their fallback instance. They should not
   define their own default URL.
4. The `.gitignore` file does not need to be updated for each new Redis
   instance.
5. The example config files are now gone as `request.yml.example` should
   be sufficient.

This instance is not used yet, but will soon be used for rate limiting
via Rack::Attack and Gitlab::ApplicationRateLimiter. Having this
configuration option in place will allow us to build on that, and also
create merge requests to support this option in Omnibus and our Helm
charts.