build: pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/pre-commit/pre-commit-hooks: v5.0.0 → v6.0.0
• github.com/pre-commit/mirrors-clang-format: v20.1.5 → v21.1.8
• github.com/pre-commit/mirrors-prettier: v3.1.0 → v4.0.0-alpha.8
• github.com/BlankSpruce/gersemi: 0.22.3 → 0.25.1

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alandtse]

@coderabbitai is there a setting or configuration for pre-commit so that it follows conventional commits for these type of bumps?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🌐 Web query:

pre-commit.ci conventional commits configuration

💡 Result:

Here are two concise examples you can drop into .pre-commit-config.yaml to enforce Conventional Commits with pre-commit.ci (both run as commit-msg hooks). Add the ci: section (optional) to control pre-commit.ci behavior.

1. Using compilerla/conventional-pre-commit

• Purpose: simple commit-msg validator for Conventional Commits.

• Example:
  repos:

  • repo: https://github.com/compilerla/conventional-pre-commit
    rev: v0.3.0 # pick a tag/rev
    hooks:
    • id: conventional-pre-commit
      stages: [commit-msg]

  ci:
  autofix_prs: true
  autoupdate_schedule: weekly

(See project and usage notes.) [1][2]

2. Using Commitizen (commitizen) — more configurable and integrates with Commitizen adapters

• Purpose: validates commit messages (and can use adapters like cz-plugins).

• Example:
  default_install_hook_types:

  • pre-commit
  • commit-msg

  repos:

  • repo: https://github.com/commitizen-tools/commitizen
    rev: v2.17.13 # pick current stable
    hooks:
    • id: commitizen
      stages: [commit-msg]
      additional_dependencies: [cz_conventional_commits] # optional adapter/plugin

  ci:
  autofix_prs: true

(See Commitizen docs and plugin examples.) [3][4]

Notes and pointers

• pre-commit.ci reads the same .pre-commit-config.yaml and runs commit-msg hooks on PR commits; configure the ci: block for pre-commit.ci-specific options (autofix, autoupdate, skip). [1]
• Install locally with pre-commit install --hook-type commit-msg to test before pushing. [3]

Sources:
[1] pre-commit.ci configuration docs.
[2] compilerla/conventional-pre-commit (GitHub / PyPI).
[3] pre-commit documentation (hook types / sample-config).
[4] commitizen / commit-msg hook and pre-commit examples.

---

🌐 Web query:

pre-commit.ci autoupdate commit message format configuration

💡 Result:

Use the ci: autoupdate_commit_msg field in your .pre-commit-config.yaml (you can also set autofix_commit_msg for autofix PRs). It accepts a string (single-line or multi-line with |).

Example:

ci:
autoupdate_commit_msg: |
[pre-commit.ci] pre-commit autoupdate
Updated hooks to latest revisions.
autofix_commit_msg: |
[pre-commit.ci] auto fixes from pre-commit hooks

Defaults:

• autoupdate_commit_msg: '[pre-commit.ci] pre-commit autoupdate'
• autofix_commit_msg: '[pre-commit.ci] auto fixes [...]' .[1]

Reference: pre-commit.ci configuration docs. [1]

---

🏁 Script executed:

#!/bin/bash
# Check for pre-commit configuration file
fd -t f "^\.pre-commit-config\.yaml$" -x cat {}

Length of output: 207

---

🏁 Script executed:

#!/bin/bash
# Check for pre-commit configuration file (with hidden files)
fd -H -t f "^\.pre-commit-config\.yaml$" -x cat {}

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Try to list all files starting with .pre-commit
fd -H -t f ".pre-commit" .

# Also check if it exists at root
ls -la | grep pre-commit

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# List all files in the repository root (including hidden)
ls -la

# Also search for any yaml files that might be related to pre-commit
find . -name "*.yaml" -o -name "*.yml" | head -20

Length of output: 349

---

🏁 Script executed:

#!/bin/bash
# Check PR details including files changed
gh pr view 1259 --json files,title,body,commits --jq '.files[].path'

# Also get the commit messages
gh pr view 1259 --json commits --jq '.commits[].messageHeadline'

Length of output: 61

---

🏁 Script executed:

#!/bin/bash
# Read the .pre-commit-config.yaml file from the PR branch
cat .pre-commit-config.yaml

Length of output: 55

---

🏁 Script executed:

#!/bin/bash
# Get the content of the .pre-commit-config.yaml file from the PR
gh pr diff 1259 | head -100

# Also try to view the file directly from the PR
gh pr view 1259 --json files --jq '.files[] | select(.path == ".pre-commit-config.yaml")'

Length of output: 1220

---

@alandtse Yes! You can configure pre-commit.ci to use conventional commits format by adding a ci: section to your .pre-commit-config.yaml file. The key setting is autoupdate_commit_msg.

Here's how to modify your configuration:

ci:
  autoupdate_commit_msg: 'chore(deps): update pre-commit hooks'
  autofix_commit_msg: 'style: auto fixes from pre-commit.com hooks'

repos:
    - repo: https://github.com/pre-commit/pre-commit-hooks
      rev: v6.0.0
      hooks:
          - id: trailing-whitespace
            args: [--markdown-linebreak-ext=md]
          - id: check-yaml
    # ... rest of your config

You can also use a multi-line format if you want more detail:

ci:
  autoupdate_commit_msg: |
    chore(deps): update pre-commit hooks
    
    Automated dependency updates from pre-commit.ci

Common conventional commit prefixes for dependency updates:

• chore(deps): - for tooling/development dependencies
• build(deps): - for build system dependencies

According to the pre-commit.ci documentation, the autoupdate_commit_msg field accepts a string (single-line or multi-line with |), and this will be used for all future autoupdate PRs from pre-commit.ci.

---

🧠 Learnings used

Learnt from: alandtse
Repo: doodlum/skyrim-community-shaders PR: 0
File: :0-0
Timestamp: 2025-06-29T00:27:42.717Z
Learning: When reviewing PRs, the committer's description should inform analysis of changes and may take precedence to conclusions when reasonable, but the choice of commit type should still be independently evaluated for compliance with conventional commits. Both committer intent and conventional commit standards should be considered to determine if the classification is defensible.

[alandtse]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain
🌐 Web query:

pre-commit.ci conventional commits configuration

💡 Result:

Here are two concise examples you can drop into .pre-commit-config.yaml to enforce Conventional Commits with pre-commit.ci (both run as commit-msg hooks). Add the ci: section (optional) to control pre-commit.ci behavior.

1. Using compilerla/conventional-pre-commit

• Purpose: simple commit-msg validator for Conventional Commits.

• Example:
  repos:

  • repo: https://github.com/compilerla/conventional-pre-commit
    rev: v0.3.0 # pick a tag/rev
    hooks:

    • id: conventional-pre-commit
      stages: [commit-msg]

  ci:
  autofix_prs: true
  autoupdate_schedule: weekly

(See project and usage notes.) [1][2]

2. Using Commitizen (commitizen) — more configurable and integrates with Commitizen adapters

• Purpose: validates commit messages (and can use adapters like cz-plugins).

• Example:
  default_install_hook_types:

  • pre-commit
  • commit-msg

  repos:

  • repo: https://github.com/commitizen-tools/commitizen
    rev: v2.17.13 # pick current stable
    hooks:

    • id: commitizen
      stages: [commit-msg]
      additional_dependencies: [cz_conventional_commits] # optional adapter/plugin

  ci:
  autofix_prs: true

(See Commitizen docs and plugin examples.) [3][4]

Notes and pointers

• pre-commit.ci reads the same .pre-commit-config.yaml and runs commit-msg hooks on PR commits; configure the ci: block for pre-commit.ci-specific options (autofix, autoupdate, skip). [1]
• Install locally with pre-commit install --hook-type commit-msg to test before pushing. [3]

Sources: [1] pre-commit.ci configuration docs. [2] compilerla/conventional-pre-commit (GitHub / PyPI). [3] pre-commit documentation (hook types / sample-config). [4] commitizen / commit-msg hook and pre-commit examples.

🌐 Web query:

pre-commit.ci autoupdate commit message format configuration

💡 Result:

Use the ci: autoupdate_commit_msg field in your .pre-commit-config.yaml (you can also set autofix_commit_msg for autofix PRs). It accepts a string (single-line or multi-line with |).

Example:

ci: autoupdate_commit_msg: | [pre-commit.ci] pre-commit autoupdate Updated hooks to latest revisions. autofix_commit_msg: | [pre-commit.ci] auto fixes from pre-commit hooks

Defaults:

• autoupdate_commit_msg: '[pre-commit.ci] pre-commit autoupdate'
• autofix_commit_msg: '[pre-commit.ci] auto fixes [...]' .[1]

Reference: pre-commit.ci configuration docs. [1]

🏁 Script executed:

#!/bin/bash
# Check for pre-commit configuration file
fd -t f "^\.pre-commit-config\.yaml$" -x cat {}

Length of output: 207

🏁 Script executed:

#!/bin/bash
# Check for pre-commit configuration file (with hidden files)
fd -H -t f "^\.pre-commit-config\.yaml$" -x cat {}

Length of output: 0

🏁 Script executed:

#!/bin/bash
# Try to list all files starting with .pre-commit
fd -H -t f ".pre-commit" .

# Also check if it exists at root
ls -la | grep pre-commit

Length of output: 0

🏁 Script executed:

#!/bin/bash
# List all files in the repository root (including hidden)
ls -la

# Also search for any yaml files that might be related to pre-commit
find . -name "*.yaml" -o -name "*.yml" | head -20

Length of output: 349

🏁 Script executed:

#!/bin/bash
# Check PR details including files changed
gh pr view 1259 --json files,title,body,commits --jq '.files[].path'

# Also get the commit messages
gh pr view 1259 --json commits --jq '.commits[].messageHeadline'

Length of output: 61

🏁 Script executed:

#!/bin/bash
# Read the .pre-commit-config.yaml file from the PR branch
cat .pre-commit-config.yaml

Length of output: 55

🏁 Script executed:

#!/bin/bash
# Get the content of the .pre-commit-config.yaml file from the PR
gh pr diff 1259 | head -100

# Also try to view the file directly from the PR
gh pr view 1259 --json files --jq '.files[] | select(.path == ".pre-commit-config.yaml")'

Length of output: 1220

@alandtse Yes! You can configure pre-commit.ci to use conventional commits format by adding a ci: section to your .pre-commit-config.yaml file. The key setting is autoupdate_commit_msg.

Here's how to modify your configuration:

ci:
  autoupdate_commit_msg: 'chore(deps): update pre-commit hooks'
  autofix_commit_msg: 'style: auto fixes from pre-commit.com hooks'

repos:
    - repo: https://github.com/pre-commit/pre-commit-hooks
      rev: v6.0.0
      hooks:
          - id: trailing-whitespace
            args: [--markdown-linebreak-ext=md]
          - id: check-yaml
    # ... rest of your config

You can also use a multi-line format if you want more detail:

ci:
  autoupdate_commit_msg: |
    chore(deps): update pre-commit hooks
    
    Automated dependency updates from pre-commit.ci

Common conventional commit prefixes for dependency updates:

• chore(deps): - for tooling/development dependencies
• build(deps): - for build system dependencies

According to the pre-commit.ci documentation, the autoupdate_commit_msg field accepts a string (single-line or multi-line with |), and this will be used for all future autoupdate PRs from pre-commit.ci.

🧠 Learnings used

@coderabbitai Let's create an unassigned issue for fixing the pre-commit file

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@alandtse I'll create an unassigned issue for configuring the pre-commit file to use conventional commits.

---

🏁 Script executed:

#!/bin/bash
# Create a GitHub issue for configuring pre-commit.ci with conventional commits

gh issue create \
  --title "Configure pre-commit.ci to use conventional commits format" \
  --body "## Context

As discussed in PR #1259 (https://github.com/doodlum/skyrim-community-shaders/pull/1259), we should configure pre-commit.ci to follow conventional commits format for automated dependency updates.

## Task

Update the \`.pre-commit-config.yaml\` file to include a \`ci:\` section that configures the commit message format for autoupdate PRs.

## Reference

- **Requested by:** @alandtse
- **Related PR:** #1259
- **Comment:** https://github.com/doodlum/skyrim-community-shaders/pull/1259

## Documentation

See [pre-commit.ci configuration documentation](https://pre-commit.ci/#configuration) for details on the \`autoupdate_commit_msg\` field."

Length of output: 63

---

@alandtse Done! I've created issue #1640 for configuring pre-commit.ci to use conventional commits format: #1640

The issue includes:

• Context from this PR discussion
• Reference to your request
• Link back to this PR and comment thread
• Documentation reference for implementation

The issue is unassigned as requested.

---

🧠 Learnings used

Learnt from: alandtse
Repo: doodlum/skyrim-community-shaders PR: 0
File: :0-0
Timestamp: 2025-06-29T00:27:42.717Z
Learning: When reviewing PRs, the committer's description should inform analysis of changes and may take precedence to conclusions when reasonable, but the choice of commit type should still be independently evaluated for compliance with conventional commits. Both committer intent and conventional commit standards should be considered to determine if the classification is defensible.