Add bulk data seed and test step
Use two jobs
Create Data Seeder docker files and docs

This script was dropped in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124875, but it
would caught an issue with executing Git inside the `vendor/gems`
directory. The `gems` directory no longer needs this each project
inherits from `gems/gem.gitlab-ci.yml`, which already enables the
`Gemspec/AvoidExecutingGit` Rubocop rule.

By moving most of the CSS compilation to a lib file, we will be able to
reuse it more easily in some other scripts.

* Run CI job per supported Ruby version.
* Use the much faster RubyVM::InstructionSequence.compile

Spawning Ruby processes is expensive and RubyVM::InstructionSequence.compile
provides the same functionality (minus warnings).

* Add Rakefile again and adjust specs
* CI: Run ruby_syntax job in preflight stage

Note that this also removes clusterwide-db for FOSS because it's not
passing for EE anyway.

Also note that this can make the pipelines run much more FOSS jobs
because previously we might only run partial FOSS jobs like
build-assets-image, but now when we run it will run all the
corresponding FOSS jobs.

We can tweak the rules accordingly in the next iteration. For this
iteration this is focusing on bringing everything over, and it should
avoid missing jobs unless there's a good reason like clusterwide-db jobs
can't pass anyway.

This reverts merge request !141897

Note that this also removes clusterwide-db for FOSS because it's not
passing for EE anyway.

Also note that this can make the pipelines run much more FOSS jobs
because previously we might only run partial FOSS jobs like
build-assets-image, but now when we run it will run all the
corresponding FOSS jobs.

We can tweak the rules accordingly in the next iteration. For this
iteration this is focusing on bringing everything over, and it should
avoid missing jobs unless there's a good reason like clusterwide-db jobs
can't pass anyway.

Add cssbundling-rails and remove sassc-rails from the GitLab project.

`cssbundling-rails` enhances `assets:precompile` to invoke `yarn
build:css`. Ran the setup command for `cssbundling-rails

Added a rudimentary `build-css` script to compile assets using Dart Sass
NodeJS

because `sassc-rails` is not being used, we have to load
`sprockets/railtie` ourselves

Changelog: changed

Pre-16.3 migration files were removed and schema
changes moved to db/init_structure.sql file

Changelog: changed

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>

When a file in the documentation is moved, the old
path was also passed to markdownlint and vale.
That causes the linting to fail, because the files
don't exist.

In order to fix that, the new option will only return
the new paths of the changed files and not the old paths.

- Adds a job that triggers a multi-project pipeline in the
code-suggestion-scenarios project

Stan Hu 创作于 1 year ago ，Lin Jen-Shin 提交于 1 year ago

This commit fixes two types of Rubocop failures seen only with Ruby 3.2:

* Style/ArgumentsForwarding: As explained in
  https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Style/ArgumentsForwarding,
  in Ruby 3.2, anonymous args/kwargs forwarding has been added. This cop can
  be disabled by setting `UseAnonymousForwarding: false`.

* Lint/RedundantRequireStatement: As explained in
  https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Lint/RedundantRequireStatement,
  `require 'set'` is no longer needed in Ruby 3.2. But since we still
  need to support Ruby 3.1 and earlier, disable this cop on `require 'set'`
  lines.

Relates to
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/140815#note_1712305597

Because those 2 tests will look up all the templates in the directory.

This script attempts to detect unused helper methods.

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

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

Replaces rails generator for supporting engineers
in creating internal events, metrics, and instrumenting
app code.

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

Pre-16.3 migration files were removed and schema
changes moved to db/init_structure.sql file

Changelog: changed

This way `spec/models/every_model_spec.rb` is run in "fast fail" job(s)
whenever a model changes.

Additional rule fix