Skip to content

chore: update pre-commit hook versions#43

Open
gamaware wants to merge 1 commit into
mainfrom
chore/update-pre-commit-hooks
Open

chore: update pre-commit hook versions#43
gamaware wants to merge 1 commit into
mainfrom
chore/update-pre-commit-hooks

Conversation

@gamaware

@gamaware gamaware commented Jun 21, 2026

Copy link
Copy Markdown
Owner

Automated update of pre-commit hook versions.

Review the changes to .pre-commit-config.yaml and merge if CI passes.

Summary by CodeRabbit

  • Chores
    • Updated development tooling configuration.

Copilot AI review requested due to automatic review settings June 21, 2026 00:28
@coderabbitai

coderabbitai Bot commented Jun 21, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The markdownlint-cli pre-commit hook version is bumped from v0.48.0 to v0.49.0 in .pre-commit-config.yaml. No other configuration changes are made.

Changes

markdownlint-cli Pre-commit Hook Version Bump

Layer / File(s) Summary
markdownlint-cli rev bump
.pre-commit-config.yaml
The rev field for the markdownlint-cli hook is updated from v0.48.0 to v0.49.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Poem

A single line changed, a version now new,
The markdown-lint rabbit hops up to v0.49! 🐇
From .48 to .49, a small little leap,
The linting stays sharp, the configs asleep.
One line bumped with care — hooray, we are done! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating pre-commit hook versions in the configuration file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-pre-commit-hooks

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the markdownlint-cli pre-commit hook version to keep local Markdown linting aligned with the latest upstream release.

Changes:

  • Bump igorshubovych/markdownlint-cli hook from v0.48.0 to v0.49.0.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
.pre-commit-config.yaml (1)

54-58: ⚖️ Poor tradeoff

Consider tooling consistency between pre-commit and CI.

The pre-commit hook uses markdownlint-cli while the CI workflow (from context snippet 2) uses markdownlint-cli2-action. These are different tools with potentially different rule sets and behaviors, which could lead to inconsistent linting results between local development and CI.

Consider standardizing on one tool (markdownlint-cli2 is generally faster and more configurable) or ensuring both are configured with identical rules to prevent discrepancies.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.pre-commit-config.yaml around lines 54 - 58, Update the markdownlint
pre-commit hook in the .pre-commit-config.yaml file to use the same tool as your
CI workflow. The markdownlint hook entry that uses the
igorshubovych/markdownlint-cli repository should be replaced with
markdownlint-cli2 configuration (or alternatively, ensure both the pre-commit
hook and your CI workflow use identical versions and configurations of
markdownlint-cli to prevent discrepancies). Verify that the args and all linting
rules are consistent between your local pre-commit setup and your CI pipeline to
ensure uniform linting behavior.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.pre-commit-config.yaml:
- Around line 54-58: Update the markdownlint pre-commit hook in the
.pre-commit-config.yaml file to use the same tool as your CI workflow. The
markdownlint hook entry that uses the igorshubovych/markdownlint-cli repository
should be replaced with markdownlint-cli2 configuration (or alternatively,
ensure both the pre-commit hook and your CI workflow use identical versions and
configurations of markdownlint-cli to prevent discrepancies). Verify that the
args and all linting rules are consistent between your local pre-commit setup
and your CI pipeline to ensure uniform linting behavior.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3ee2f5ef-770e-4aa3-919d-3829244dd958

📥 Commits

Reviewing files that changed from the base of the PR and between e8fe3d4 and 78641cf.

📒 Files selected for processing (1)
  • .pre-commit-config.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants