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

The debugging tasks are added to check whether RuboCop cache works as
expected or not.
Signed-off-by: Rémy Coutable <remy@rymai.me>

- This allows us to quickly run this for specific
  file paths
- Also updates previous references (i.e. CI) to
  add "."
- Also removes lefthook reference to
  `yarn run internal...`
- Also adds `:all` and `:all:fix` scripts

Replace all scss-lint mentions with stylelint.

Similar to `eslint`, this moves our `prettier` related scripts to the
`lint` scope. We keep the old scripts in place and error out
immediately, hinting the user to the new scripts.

Thanks to the introduced `scripts/frontend/execute-on-staged-files.sh`
and the fact that `prettier` itself has implemented better command line
interfaces (`--check` and `--write`) since we introduced it, we are able
to remove our home made node script in favor of those.

Now the scripts carry the following names:

 - `prettier-all` => `lint:prettier`
 - `prettier-all-save` => `lint:prettier:fix`
 - `prettier-staged` => `lint:prettier:staged`
 - `prettier-staged-save`: `lint:prettier:staged:fixed`

We are currently overloading the `eslint` command with our custom eslint
logic. Unfortunately this causes us to run `eslint` on all js/vue files
and makes it hard to run custom eslint commands. One has to resort to
running e.g. `node_modules/.bin/eslint` directly.

In an effort to consolidate the situation we are renaming the commands
(borrowing from our rake syntax) as follows:

- `eslint` => `lint:eslint`
- `eslint-fix` => `lint:eslint:fix`
- `eslint-staged` => `lint:eslint:staged`
- `eslint-staged-fix` => `lint:eslint:staged:fix`
- `eslint-report` => `lint:eslint:report`

All but the `eslint` command have been replaced with a command that
errors out immediately and hints folks to the new command.

Auto-corrected with Rubocop

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

This reverts merge request !20521

These are causing warnings about already initialized constants
because the class is loaded twice

Also adds a script-analysis script to check for
blocked dependencies in package.json

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

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

This job checks that files in the unreleased changelogs directories have
the correct .yml extension. It ignores the .gitkeep files already there.

This adds a minor performance optimization to avoid allocation of an
array.

As seen in https://gitlab.com/gitlab-org/gitlab/-/jobs/394057944,
static-analysis is failing with:

```
Browserslist: caniuse-lite is outdated. Please run next command
`yarn upgrade`
```

The problem may be occurring because browserslist is detecting that
caniuse-list is approximately 6 months old and outputs a warning using
console.warn.

To fix this, we change static-analysis to filter this warning message
when deciding to exit with error code 2. Older GitLab backports
shouldn't fail because we need to upgrade this dependency.

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

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

This code is no longer needed in the single codebase setup.

This backport changes made by EE to the files in the scripts/ directory.
This comes with a few changes to some scripts to make them work in the
single codebase setup.

This backport changes made by EE to the files in the scripts/ directory.
This comes with a few changes to some scripts to make them work in the
single codebase setup.

Added stylelint to static-analysis
Updated yarn dependencies
CSS Fixes and rule adoptions of stylelint
Added stylelint-scss
Deduplicated yarn.lock to clear dependencies

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

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

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

However keep backward compatibility

Otherwise it could be confusing

TODO: fix offenders

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

When a changelog has invalid YAML (typically, there is an unquoted @ at the
start of the author field), then the entry will be discarded. This script checks
all unreleased changelogs for validity, and runs as part of the static-analysis
step, so the pipeline will fail if this happens in future.