Node v24 changes the way that modules are loaded, and this includes the commitlint config file. If your project does not contain a package.json, commitlint may fail to load the config, resulting in a Please add rules to your commitlint.config.js error message.

To get the most out of commitlint you'll want to automate it in your project lifecycle.

September 8, 2023 - What is Commitlint? Commitlint is a simple tool that lints your commit messages and makes sure they follow a set of rules. It runs as a…

June 4, 2024 - Commitlint is the ESLint for your commit messages. It performs validations on any text against a predefined commit format.

March 15, 2026 - Lint your commit messages. Latest version: 20.5.0, last published: a month ago. Start using commitlint in your project by running `npm i commitlint`. There are 121 other projects in the npm registry using commitlint.

February 22, 2026 - commitlint checks if your commit message meets the conventional commit format

October 23, 2023 - Commitlint maintains consistent formatting and style for commit messages in version control systems like Git.

March 15, 2026 - Shareable commitlint config enforcing conventional commits. Latest version: 20.5.0, last published: a month ago. Start using @commitlint/config-conventional in your project by running `npm i @commitlint/config-conventional`. There are 1374 other projects in the npm registry using ...

types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.

Commit conventions allow your team to add more semantic meaning to your git history. This e.g. includes type, scope or breaking changes. With this additional information tools can derive useful human-readable information for releases of your project. Some examples are ... Commitlint supports multiple scopes.

November 12, 2021 - Commitlint is a simple tool that lints your commit messages and makes sure they follow a set of rules.

Every commitlint configuration can extend other commitlint configurations. Specify configurations to extend via the .extends key, using ids that can be resolved by the node resolve algorithm. This means installed npm packages and local files can be used.

September 12, 2023 - The following are all the types that commitlint suggests and provides including the example commit: build --> Changes that affect the build system or external dependencies ... style --> Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)

November 18, 2019 - Commitlint is just a tool for checking if your messages follow your conventions. It does not force you to use a specific convention, you can use whatever you want, it is fully configurable. It offers some configurations out of the box.

Node v24 changes the way that modules are loaded, and this includes the commitlint config file. If your project does not contain a package.json, commitlint may fail to load the config, resulting in a Please add rules to your commitlint.config.js error message.

commitlint: A linter to check that your commit messages meet the Conventional Commits format.

February 24, 2026 - yarn add -D husky # Activate husky yarn husky install # Add the hook yarn husky add .husky/commit-msg "yarn commitlint --edit $1"

To use commitlint you need to setup commit-msg hook (currently pre-commit hook is not supported) To lint commits before they are created you can use Husky's commit-msg hook. You can find complete setup instructions on the official documentation. ... The following instructions are meant to husky@v9 ...

name: CI on: [push, pull_request] permissions: contents: read jobs: commitlint: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 with: fetch-depth: 0 - name: Setup node uses: actions/setup-node@v4 with: node-version: lts/* cache: npm - name: Install commitlint run: npm install -D @commitlint/cli @commitlint/config-conventional - name: Print versions run: | git --version node --version npm --version npx commitlint --version - name: Validate current commit (last commit) with commitlint if: github.event_name == 'push' run: npx commitlint --last --verbose - name: Validate PR commits with commitlint if: github.event_name == 'pull_request' run: npx commitlint --from ${{ github.event.pull_request.base.sha }} --to ${{ github.event.pull_request.head.sha }} --verbose

We cannot provide a description for this page right now