Skip to content

docs(hooks): warn that pre-commit autoupdate pins pre-releases #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CybotTM merged 1 commit into from
Jul 17, 2026
Merged

docs(hooks): warn that pre-commit autoupdate pins pre-releases #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions skills/git-workflow/references/git-hooks-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,15 @@ Then install based on what's found:
- `.pre-commit-config.yaml` → `pre-commit install`
- Nothing → suggest adding one based on project language

## Updating Hook Versions (`pre-commit autoupdate`)

`pre-commit autoupdate` bumps every hook's `rev` to the repo's **latest tag —
including pre-releases**. It happily pins a beta (observed: isort
`8.0.1 → 9.0.0b1`). After running it, review each bumped `rev` and pin any
`aN`/`bN`/`rcN` back to the latest stable tag before committing. When a hook
mirrors a locked dev dependency (black, isort), keep the hook `rev` aligned
with the lockfile version instead of blindly taking the newest tag.

## Recommended Hooks by Stage

### pre-commit (fast, <5s)
Expand Down
Loading