chore: switch from gitlint to committed

For nice single binary install, one Python dependency fewer.

Re .config/, https://github.com/pi0/config-dir
committed is expected to run only from within git hooks,
so we have the luxury to specify a path to the config.

Author: scop

.config/committed.toml

@@ -0,0 +1,3 @@
+style = "conventional"
+ignore_author_re = '\[bot\]'
+subject_capitalized = false

.github/renovate.json

@@ -40,13 +40,6 @@
       "commitMessageTopic": "{{depName}}",
       "semanticCommitScope": "pre-commit"
     },
-    {
-      "versioning": "pep440",
-      "groupName": "gitlint",
-      "matchPackageNames": [
-        "/(^|/)gitlint$/"
-      ]
-    },
     {
       "matchPackageNames": [
         "perltidy/perltidy"

.github/requirements.txt

@@ -1,4 +1,3 @@
 -r ../test/requirements-dev.txt
 
-gitlint==0.19.1
 pre-commit>=3.2.0

.github/workflows/ci.yaml

@@ -13,10 +13,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: # for gitlint
+        with:
           persist-credentials: false
-          ref: ${{ github.event.pull_request.head.sha }}
-          fetch-depth: 0
       - uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c # v6.0.0
         with:
           python-version: ">=3.7"
@@ -33,8 +31,6 @@ jobs:
           python3 -m venv venv  # for venv-run
           source venv/bin/activate
           python3 -m pip install -Ur .github/requirements.txt
-      - run: venv/bin/gitlint --commits "origin/$GITHUB_BASE_REF..HEAD"
-        if: github.event_name == 'pull_request'
       - name: Run pre-commit checks
         run: |
           source venv/bin/activate

.github/workflows/lint-commits.yaml

@@ -0,0 +1,23 @@
+name: Lint commits
+
+on:
+  pull_request:
+
+permissions: {}
+
+jobs:
+  lint-commits:
+    name: Lint commits
+    runs-on: ubuntu-latest
+    env:
+      FORCE_COLOR: true
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - uses: crate-ci/committed@bb02f309663f9baced8dbd5fdd80c6369ddf3efd # v1.1.8
+        with:
+          args: "-vv --no-merge-commit --config=.config/committed.toml"

.gitlint

@@ -3,10 +3,15 @@ minimum_pre_commit_version: 3.2.0 # for "default_stages" names
 
 repos:
 
-  - repo: https://github.com/jorisroovers/gitlint
-    rev: v0.19.1
+  - repo: https://github.com/crate-ci/committed
+    rev: v1.1.8
     hooks:
-      - id: gitlint
+      - id: committed
+        args:
+          - --config=.config/committed.toml
+          - --fixup
+          - --wip
+          - --commit-file
 
   - repo: https://github.com/scop/pre-commit-shfmt
     rev: v3.12.0-2

.pre-commit-config.yaml

@@ -173,10 +173,12 @@ Also, please bear the following coding guidelines in mind:
   unrelated changes into a single commit.
 
 - We use [Conventional Commits](https://www.conventionalcommits.org/)
-  to format commit messages, with types and most other details from
-  [commitlint's config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional).
-  `gitlint` in our pre-commit config checks commit messages for
-  conformance with these rules.
+  to format commit messages.
+  [`committed`](https://github.com/crate-ci/committed)
+  is the tool we use in our pre-commit linting to check
+  commit messages, using most of
+  [its default rules](https://github.com/crate-ci/committed/blob/master/docs/reference.md#config-fields),
+  in particular the conventional commit types.
 
   It is important to do this correctly; commit types `fix` and `feat`
   as well as any change marked as breaking affects what ends up in the