git-commit-guard 0.22.2__tar.gz → 0.23.0__tar.gz

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/coverage-baseline.yml

@@ -16,7 +16,7 @@ jobs:
           persist-credentials: false
       - name: Install uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # ratchet:astral-sh/setup-uv@v7
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # ratchet:astral-sh/setup-uv@v8.2.0
       - name: Cache NLTK data
         # yamllint disable-line rule:line-length
         uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7  # v5.0.4
@@ -27,7 +27,7 @@ jobs:
         run: uv run --dev pytest tests/ --cov=git_commit_guard --cov-report=xml
       - name: Upload coverage baseline
         # yamllint disable-line rule:line-length
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02  # ratchet:actions/upload-artifact@v4
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a  # ratchet:actions/upload-artifact@v7
         with:
           name: main-coverage
           path: coverage.xml

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/coverage-comment.yml

@@ -16,7 +16,7 @@ jobs:
     steps:
       - name: Download artifact
         # yamllint disable-line rule:line-length
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093  # ratchet:actions/download-artifact@v4
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c  # ratchet:actions/download-artifact@v8
         with:
           run-id: ${{ github.event.workflow_run.id }}
           name: pr
@@ -57,7 +57,7 @@ jobs:
       - name: Download baseline coverage
         if: steps.baseline.outputs.run-id != ''
         # yamllint disable-line rule:line-length
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093  # ratchet:actions/download-artifact@v4
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c  # ratchet:actions/download-artifact@v8
         with:
           run-id: ${{ steps.baseline.outputs.run-id }}
           name: main-coverage

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/lint-commits.yml

@@ -22,6 +22,6 @@ jobs:
           key: nltk-averaged-perceptron-tagger-punkt
       - name: Lint commits
         # yamllint disable-line rule:line-length
-        uses: benner/commit-guard@9162df75e7a6eba395bf7c07c1a0952fc6d04ea0  # v0.22.1
+        uses: benner/commit-guard@4f989e92ddf04153ec33040da42bc2f788c71584  # v0.22.3
         with:
           range: origin/${{ github.base_ref }}..HEAD

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/lint-md.yml

@@ -37,7 +37,7 @@ jobs:
           persist-credentials: false
       - name: Set up uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # v7.6.0
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
         with:
           enable-cache: false
       - name: Set up reviewdog

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/lint-workflows.yml

@@ -34,7 +34,7 @@ jobs:
           persist-credentials: false
       - name: Set up uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # ratchet:astral-sh/setup-uv@v7
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # ratchet:astral-sh/setup-uv@v8.2.0
       - name: Set up reviewdog
         # yamllint disable-line rule:line-length
         uses: reviewdog/action-setup@d8a7baabd7f3e8544ee4dbde3ee41d0011c3a93f  # ratchet:reviewdog/action-setup@v1
@@ -59,7 +59,7 @@ jobs:
           persist-credentials: false
       - name: Set up uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # ratchet:astral-sh/setup-uv@v7
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # ratchet:astral-sh/setup-uv@v8.2.0
       - name: Set up reviewdog
         # yamllint disable-line rule:line-length
         uses: reviewdog/action-setup@d8a7baabd7f3e8544ee4dbde3ee41d0011c3a93f  # ratchet:reviewdog/action-setup@v1

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/release.yml

@@ -20,7 +20,7 @@ jobs:
           fetch-depth: 0
       - name: Set up uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # v7.6.0
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
         with:
           enable-cache: false
       - name: Build package

git_commit_guard-0.23.0/.github/workflows/security-audit.yml

@@ -0,0 +1,69 @@
+---
+name: Security Audit
+on:  # yamllint disable-line rule:truthy
+  pull_request:
+  schedule:
+    - cron: 13 3 * * *
+permissions:
+  contents: read
+jobs:
+  audit:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+    steps:
+      - name: Checkout code
+        # yamllint disable-line rule:line-length
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
+        with:
+          persist-credentials: false
+      - name: Install uv
+        # yamllint disable-line rule:line-length
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
+      - name: Audit dependencies
+        run: |
+          set -o pipefail
+          uv audit --frozen --preview-features audit-command 2>&1 |
+            tee audit.log
+      - name: Report failure in a tracking issue
+        if: failure() && github.event_name == 'schedule'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          GH_REPO: ${{ github.repository }}
+        run: |
+          run_url="$GITHUB_SERVER_URL/$GITHUB_REPOSITORY"
+          run_url="$run_url/actions/runs/$GITHUB_RUN_ID"
+          {
+            echo "Scheduled security audit failed: $run_url"
+            echo
+            echo '```'
+            cat audit.log
+            echo '```'
+            echo
+            echo '<!-- security-audit -->'
+          } > issue-body.md
+          issue=$(gh issue list --state open \
+            --search 'Security audit failing in:title' \
+            --json number --jq '.[0].number')
+          if [ -n "$issue" ]; then
+            gh issue comment "$issue" --body-file issue-body.md
+          else
+            gh issue create --title "Security audit failing" \
+              --body-file issue-body.md
+          fi
+      - name: Close the tracking issue
+        if: success() && github.event_name == 'schedule'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          GH_REPO: ${{ github.repository }}
+        run: |-
+          run_url="$GITHUB_SERVER_URL/$GITHUB_REPOSITORY"
+          run_url="$run_url/actions/runs/$GITHUB_RUN_ID"
+          issue=$(gh issue list --state open \
+            --search 'Security audit failing in:title' \
+            --json number --jq '.[0].number')
+          if [ -n "$issue" ]; then
+            gh issue close "$issue" \
+              --comment "Scheduled security audit is green again: $run_url"
+          fi

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/.github/workflows/test.yml

@@ -15,7 +15,7 @@ jobs:
           persist-credentials: false
       - name: Install uv
         # yamllint disable-line rule:line-length
-        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78  # v7.6.0
+        uses: astral-sh/setup-uv@fac544c07dec837d0ccb6301d7b5580bf5edae39  # v8.2.0
       - name: Cache NLTK data
         uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7  # v5.0.4
         with:
@@ -35,7 +35,7 @@ jobs:
           cp coverage.xml ./pr/
       - name: Upload PR artifact
         # yamllint disable-line rule:line-length
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02  # ratchet:actions/upload-artifact@v4
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a  # ratchet:actions/upload-artifact@v7
         with:
           name: pr
           path: pr/

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: git-commit-guard
-Version: 0.22.2
+Version: 0.23.0
 Summary: Opinionated conventional commit message linter with imperative mood detection
 Project-URL: Homepage, https://github.com/benner/commit-guard
 Project-URL: Repository, https://github.com/benner/commit-guard
@@ -36,7 +36,7 @@ Opinionated conventional commit message linter with imperative mood detection.
   verb, verified via nltk POS tagging — not a hand-coded regex of "bad"
   words.
 * **Signature verification without a local keyring.** Resolves the commit
-  author via the GitHub API and verifies GPG/SSH against their published
+  committer via the GitHub API and verifies GPG/SSH against their published
   `.gpg`/`.keys` — no per-runner key management.
 * **Strict by default.** Subject format, body, trailers, `Signed-off-by`,
   and signature all enforced out of the box; opt out with `--disable`.
@@ -242,7 +242,7 @@ independently of `--enable`/`--disable`.
 The `signature` check verifies the commit without any local keyring setup:
 
 1. If the repo has a GitHub remote, call the Commits API
-   (`GET /repos/{owner}/{repo}/commits/{sha}`) to resolve the author's GitHub
+   (`GET /repos/{owner}/{repo}/commits/{sha}`) to resolve the committer's GitHub
    username — this works for corporate emails, noreply addresses, or any email
    not listed publicly on a GitHub profile.
 2. If the Commits API is unavailable (no GitHub remote, commit not yet pushed,
@@ -250,7 +250,7 @@ The `signature` check verifies the commit without any local keyring setup:
    (`{id}+{username}@users.noreply.github.com` or
    `{username}@users.noreply.github.com`) — no API call needed.
 3. If neither of the above resolves a username, fall back to searching GitHub
-   by the commit author's email.
+   by the commit committer's email.
 4. Fetch the resolved user's public keys from `github.com/{username}.gpg`
    (GPG) and the `/users/{username}/ssh_signing_keys` API (SSH keys tagged
    with the **Signing key** role). Auth-only SSH keys are deliberately not
@@ -261,7 +261,7 @@ The `signature` check verifies the commit without any local keyring setup:
    `git verify-commit` with the SSH allowed-signers config.
 7. If any key verifies, the check passes. If none do, it fails.
 
-If the author cannot be resolved via either method, or the GitHub API is
+If the committer cannot be resolved via either method, or the GitHub API is
 unreachable, the check fails with a clear error.
 
 For private repositories, set `GITHUB_TOKEN` or `GH_TOKEN` so the Commits API
@@ -316,7 +316,7 @@ COMMIT_GUARD_GIT_TIMEOUT=30 commit-guard --range origin/main..HEAD
 In GitHub Actions, set it at the step or job level:
 
 ```yaml
-- uses: benner/commit-guard@v0.22.2
+- uses: benner/commit-guard@v0.23.0
   env:
     COMMIT_GUARD_GIT_TIMEOUT: 30
   with:
@@ -352,6 +352,22 @@ misconfigured range specs in CI. Use `--allow-empty` to exit 0 instead:
 commit-guard --range origin/main..HEAD --allow-empty
 ```
 
+### Quiet mode
+
+Use `--quiet` (or `-q`) to suppress output for commits that have nothing to
+report — only commits with errors or warnings are printed. On a long range
+this leaves exactly the offending commits in the output; a fully compliant
+range prints nothing and exits 0:
+
+```bash
+commit-guard --range origin/main..HEAD --quiet
+```
+
+Quiet mode applies to single-commit and range mode, in both text and
+`--output jsonl` formats. Exit codes are unchanged, so it composes with CI
+gating. `--output-file` is not affected — the file always receives the
+complete record stream.
+
 ### Machine-readable output
 
 Use `--output jsonl` to emit one JSON line per commit to stdout instead of the
@@ -400,7 +416,7 @@ steps:
   - uses: actions/checkout@v4
     with:
       fetch-depth: 0
-  - uses: benner/commit-guard@v0.22.2
+  - uses: benner/commit-guard@v0.23.0
 ```
 
 Check all commits in a pull request:
@@ -416,7 +432,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
 ```
@@ -424,7 +440,7 @@ jobs:
 Check a specific commit SHA (mirrors the positional CLI argument):
 
 ```yaml
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           rev: ${{ github.sha }}
 ```
@@ -442,7 +458,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
           disable: signed-off,signature
@@ -462,7 +478,7 @@ jobs:
 When `output-file` is set the action exposes the path as an output:
 
 ```yaml
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         id: cg
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
@@ -478,7 +494,7 @@ Add to your `.pre-commit-config.yaml`:
 ---
 repos:
   - repo: https://github.com/benner/commit-guard
-    rev: v0.22.2
+    rev: v0.23.0
     hooks:
       - id: commit-guard
       - id: commit-guard-signature

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/README.md

@@ -15,7 +15,7 @@ Opinionated conventional commit message linter with imperative mood detection.
   verb, verified via nltk POS tagging — not a hand-coded regex of "bad"
   words.
 * **Signature verification without a local keyring.** Resolves the commit
-  author via the GitHub API and verifies GPG/SSH against their published
+  committer via the GitHub API and verifies GPG/SSH against their published
   `.gpg`/`.keys` — no per-runner key management.
 * **Strict by default.** Subject format, body, trailers, `Signed-off-by`,
   and signature all enforced out of the box; opt out with `--disable`.
@@ -221,7 +221,7 @@ independently of `--enable`/`--disable`.
 The `signature` check verifies the commit without any local keyring setup:
 
 1. If the repo has a GitHub remote, call the Commits API
-   (`GET /repos/{owner}/{repo}/commits/{sha}`) to resolve the author's GitHub
+   (`GET /repos/{owner}/{repo}/commits/{sha}`) to resolve the committer's GitHub
    username — this works for corporate emails, noreply addresses, or any email
    not listed publicly on a GitHub profile.
 2. If the Commits API is unavailable (no GitHub remote, commit not yet pushed,
@@ -229,7 +229,7 @@ The `signature` check verifies the commit without any local keyring setup:
    (`{id}+{username}@users.noreply.github.com` or
    `{username}@users.noreply.github.com`) — no API call needed.
 3. If neither of the above resolves a username, fall back to searching GitHub
-   by the commit author's email.
+   by the commit committer's email.
 4. Fetch the resolved user's public keys from `github.com/{username}.gpg`
    (GPG) and the `/users/{username}/ssh_signing_keys` API (SSH keys tagged
    with the **Signing key** role). Auth-only SSH keys are deliberately not
@@ -240,7 +240,7 @@ The `signature` check verifies the commit without any local keyring setup:
    `git verify-commit` with the SSH allowed-signers config.
 7. If any key verifies, the check passes. If none do, it fails.
 
-If the author cannot be resolved via either method, or the GitHub API is
+If the committer cannot be resolved via either method, or the GitHub API is
 unreachable, the check fails with a clear error.
 
 For private repositories, set `GITHUB_TOKEN` or `GH_TOKEN` so the Commits API
@@ -295,7 +295,7 @@ COMMIT_GUARD_GIT_TIMEOUT=30 commit-guard --range origin/main..HEAD
 In GitHub Actions, set it at the step or job level:
 
 ```yaml
-- uses: benner/commit-guard@v0.22.2
+- uses: benner/commit-guard@v0.23.0
   env:
     COMMIT_GUARD_GIT_TIMEOUT: 30
   with:
@@ -331,6 +331,22 @@ misconfigured range specs in CI. Use `--allow-empty` to exit 0 instead:
 commit-guard --range origin/main..HEAD --allow-empty
 ```
 
+### Quiet mode
+
+Use `--quiet` (or `-q`) to suppress output for commits that have nothing to
+report — only commits with errors or warnings are printed. On a long range
+this leaves exactly the offending commits in the output; a fully compliant
+range prints nothing and exits 0:
+
+```bash
+commit-guard --range origin/main..HEAD --quiet
+```
+
+Quiet mode applies to single-commit and range mode, in both text and
+`--output jsonl` formats. Exit codes are unchanged, so it composes with CI
+gating. `--output-file` is not affected — the file always receives the
+complete record stream.
+
 ### Machine-readable output
 
 Use `--output jsonl` to emit one JSON line per commit to stdout instead of the
@@ -379,7 +395,7 @@ steps:
   - uses: actions/checkout@v4
     with:
       fetch-depth: 0
-  - uses: benner/commit-guard@v0.22.2
+  - uses: benner/commit-guard@v0.23.0
 ```
 
 Check all commits in a pull request:
@@ -395,7 +411,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
 ```
@@ -403,7 +419,7 @@ jobs:
 Check a specific commit SHA (mirrors the positional CLI argument):
 
 ```yaml
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           rev: ${{ github.sha }}
 ```
@@ -421,7 +437,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
           disable: signed-off,signature
@@ -441,7 +457,7 @@ jobs:
 When `output-file` is set the action exposes the path as an output:
 
 ```yaml
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         id: cg
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
@@ -457,7 +473,7 @@ Add to your `.pre-commit-config.yaml`:
 ---
 repos:
   - repo: https://github.com/benner/commit-guard
-    rev: v0.22.2
+    rev: v0.23.0
     hooks:
       - id: commit-guard
       - id: commit-guard-signature

{git_commit_guard-0.22.2 → git_commit_guard-0.23.0}/docs/index.html

@@ -315,7 +315,7 @@
           </li>
           <li>
             <strong>Signature verification without a local keyring.</strong>
-            Resolves the commit author via the GitHub API and verifies GPG/SSH
+            Resolves the commit committer via the GitHub API and verifies GPG/SSH
             against their published <code>.gpg</code>/<code>.keys</code> — no
             per-runner key management.
           </li>
@@ -456,7 +456,7 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
         <ol>
           <li>If the repo has a GitHub remote, call the Commits API
             (<code>GET /repos/{owner}/{repo}/commits/{sha}</code>) to resolve
-            the author's GitHub username — works for corporate emails, noreply
+            the committer's GitHub username — works for corporate emails, noreply
             addresses, or any email not listed publicly on a GitHub profile.</li>
           <li>If the Commits API is unavailable (no GitHub remote, commit not
             yet pushed, or API error), parse the username directly from a
@@ -464,7 +464,7 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
             (<code>{id}+{username}@users.noreply.github.com</code>) — no API
             call needed.</li>
           <li>If neither of the above resolves a username, fall back to
-            searching GitHub by the commit author's email.</li>
+            searching GitHub by the commit committer's email.</li>
           <li>Fetch the resolved user's public keys from
             <code>github.com/{username}.gpg</code> (GPG) and
             <code>/users/{username}/ssh_signing_keys</code> (SSH keys tagged
@@ -476,7 +476,7 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
           <li>Pass if any key verifies; fail if none do.</li>
         </ol>
         <p>
-          If the author cannot be resolved via either method, or the GitHub API
+          If the committer cannot be resolved via either method, or the GitHub API
           is unreachable, the check fails with a clear error. For private
           repositories, set <code>GITHUB_TOKEN</code> or <code>GH_TOKEN</code>
           so the Commits API can authenticate. The official GitHub Action wires
@@ -551,6 +551,15 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
           readable logs and structured results for downstream steps:
         </p>
         <pre><code class="language-bash">commit-guard --range origin/main..HEAD --output-file results.jsonl</code></pre>
+        <p>
+          Use <code>--quiet</code> (or <code>-q</code>) to suppress output for
+          commits that have nothing to report — only commits with errors or
+          warnings are printed, in both text and JSONL formats. A fully
+          compliant range prints nothing and exits 0. Exit codes are unchanged,
+          and <code>--output-file</code> always receives the complete record
+          stream:
+        </p>
+        <pre><code class="language-bash">commit-guard --range origin/main..HEAD --quiet</code></pre>
       </section>
 
       <section id="github-actions">
@@ -566,13 +575,13 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: benner/commit-guard@v0.22.2
+      - uses: benner/commit-guard@v0.23.0
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
           disable: signed-off,signature</code></pre>
 
         <p>Check a specific commit SHA:</p>
-        <pre><code class="language-yaml">      - uses: benner/commit-guard@v0.22.2
+        <pre><code class="language-yaml">      - uses: benner/commit-guard@v0.23.0
         with:
           rev: ${{ github.sha }}</code></pre>
 
@@ -591,7 +600,7 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
           When <code>output-file</code> is set the action exposes the path as
           a step output, making JSONL results available to subsequent steps:
         </p>
-        <pre><code class="language-yaml">      - uses: benner/commit-guard@v0.22.2
+        <pre><code class="language-yaml">      - uses: benner/commit-guard@v0.23.0
         id: cg
         with:
           range: ${{ env.PR_BASE }}..${{ env.PR_HEAD }}
@@ -604,7 +613,7 @@ require-subject-pattern = "[A-Z]+-[0-9]+"</code></pre>
         <p>Add to <code>.pre-commit-config.yaml</code>:</p>
         <pre><code class="language-yaml">repos:
   - repo: https://github.com/benner/commit-guard
-    rev: v0.22.2
+    rev: v0.23.0
     hooks:
       - id: commit-guard
       - id: commit-guard-signature</code></pre>