Maintain HISTORY.asc fixed-issues line per-commit; never force-push a PR - #63
Merged
jnasbyupgrade merged 1 commit intoJul 31, 2026
Conversation
Commit skill (step 3b, new): whenever a commit's `Fixes #N` closes a pgxntool issue, add it to the STABLE section's fixed-issues line immediately, even when the underlying change is too minor for its own narrative entry -- these are independent decisions. Previously this line was only compiled once, at release time, by scanning all merged PRs since the last release; that's now downgraded to an audit/safety net for anything that slipped through the per-commit step, rather than the primary mechanism. Release skill and the commit-message-format guide updated to match. Commit skill: made the existing "never force push" rule unambiguous -- it applies even to your own unreviewed draft PR branch, even for something as minor as fixing a HISTORY.asc entry. Add a new commit instead unless the user explicitly asks for a force-push/amend. Changes only in pgxntool-test. No related changes in pgxntool. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/commitskill (step 3b, new): whenever a commit'sFixes #Ncloses a pgxntool issue, add it toHISTORY.asc's STABLE section fixed-issues line immediately -- even when the change is too minor for its own narrative==entry. Previously this line was only compiled once, at release time, by scanning all merged PRs since the last release; that step is now downgraded to an audit/safety net for anything that slipped through, rather than the primary mechanism./releaseskill and the commit-message-format guide updated to match./commitskill: made the existing "never force push" rule unambiguous -- it applies even to your own unreviewed draft PR branch, even for something as minor as fixing aHISTORY.ascentry. Add a new commit instead unless the user explicitly asks for a force-push/amend.Changes only in pgxntool-test (
.claude/skills/process docs). No pgxntool changes.Test plan
🤖 Generated with Claude Code