docs: update CONTRIBUTING.md file
MODIFY
CONTRIBUTING.md
CONTRIBUTING.md
@@ -177,15 +177,28 @@ When creating a new pull request, it's preferable to use a conventional commit-f
Here are some other scripts that you might find useful.
-#### If you are a core contributor
+#### Run benchmarks via comments
If you are a core contributor, and you have access to create new branches
from the main repository (not a fork), use these comments to run specific workflows:
- `!bench_parser` benchmarks the parser's runtime performance and writes a comment with the results;
- `!bench_formatter` benchmarks the formatter runtime performance and writes a comment with the results;
+- `!bench_analyzer` benchmarks the analyzer runtime performance and writes a comment with the results;
-#### Naming patterns
+#### Creating rules
+
+When creating or updating lint rules, you need to be aware that there's a lot of generated code inside our toolchain, and
+our CI makes sure that this code is not out of sync. If some autogenerated files are out of sync,
+the CI will fail.
+
+Run the following commands to update the generated files:
+- `cargo codegen-configuration`, **this command must be run first** and, it will update the configuration;
+- `cargo lintdoc`, it will update the website;
+- `cargo codegen-bindings`, it will update the TypeScript types released inside the JS APIs;
+- `cargo codegen-schema`, it will update the JSON Schema file of the configuration, used by VSCode;
+
+#### Naming patterns for rules
1. Forbid a concept

docs: update CONTRIBUTING.md file (#3220)