Linting & formatting

A step of the Cloud application tree on Gradus, in the Build & ship area: Config, lint, releases, IaC.

Add a linter and formatter with a shared config, run them in CI and on commit, so style never comes up in review.

Usually comes after: Project structure & config.

Leads to: Commit conventions & review, Automated dependency updates.

Prompt for your AI assistant

Set up a linter and a code formatter for this project with a shared config, add a pre-commit hook that runs them and make the CI workflow fail on lint errors.

• Show on map
• This step as Markdown
• Every step of the tree, for AI assistants

This is https://gradus.kazet.blog/tree/cloud-application/step/lint-and-format as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.