Repository navigation
docs(pre-commit): publish supported hook design - #748
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 4 minutes. View limit details
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. Comment |
|
@codex review |
Coverage Report
File CoverageNo changed files found. |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
🎉 This PR is included in version 2.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Why
#745 intentionally shipped the provider before changing the consumer README because the existing
v2tag did not yet contain the hook. Release 2.1.0 is now published, so the public guidance can be corrected.This also fixes a deeper pre-commit design issue: a moving major tag is not a reliable
rev. pre-commit caches hook repositories by repository + revision string, so an existingrev: v2cache is not guaranteed to refresh when that tag moves.Changes
repo: localworkaround with the published hook.rev: v2.1.0andpre-commit autoupdatefor upgrades..ghadocs.json.docs/tool-contract.md: consumer Node/npm runtime, exact npm-version binding, argument forwarding, no staged filenames, and immutable release refs.AGENTS.mdinstead of treating all Git-hook work as Husky.Verification target
The existing PR-head smoke must still prove argument forwarding, mutation detection, and idempotence. The added release smoke must prove that the copy/paste
v2.1.0configuration resolves and updates the configured README while leaving the default README alone.