Linting

ESLint

Typescript / Javascript linting

commitlint

The commits semantic check is really only relevant when merging (squash&commit) PRs into main, but it is currently configured to apply to all commits.

Because the commitlint library can be very restrictive on your commit semantics, for local interin commits (only!), you may want to use the git commit --no-verify option.

Remember squashing your local commits and correct the comment so that it follows the commitlint rules before committing & pushing to origin.

For commits squash use git reset --soft instead of git rebase -i, rebase will most likely fail.

Be aware of GitHub PRs feature reviewers code suggestions: accepting & commiting suggestions using the GitHub GUI will generate commits with coauthor information in the comment that will break the commitlint rules.

semantic-release

will be triggered on commits to main.