docs(release): document refactor fragment dedup policy #986
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!986
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "i/492-refactor-bullet-policy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Option (d) from rt#492: document the bounded policy rather than add a heuristic parser. The current Go
rt preppath omits fragment-less conventional-commit subjects from the composed CHANGELOG, so the duplicate refactor-of-X class is avoided there. The documentation records the legacy/consumer edge, keeps an existing fragment as the sole note source, and documentsRefactors: #NNNas a human/audit convention. The trailer is explicitly not parsed by the current toolkit.Verification:
APPROVED — exact head
fb6548b064.Reviewed the complete two-file diff. It implements rt#492 option (d): exact filename-reference deduplication cannot infer a semantic refactor-of-X relationship when the numbers differ; the current Go rt prep path omits fragment-less conventional-commit subjects from composed notes while retaining their bump signal; and
Refactors: #NNNis documented as an audit convention explicitly not parsed by release-toolkit. Legacy release-prep consumers and historical cuts are clearly separated from the current Go behavior, and the historical relationship is retained without promising an unimplemented suppression mechanism.Independent verification on this head: go test -count=1 ./...; go vet ./...; Bats 99/99; fragment-check PASS; register-check 0; dated-examples-check PASS; git diff --check PASS; all 21 latest status contexts success. Added lines and commit messages contain no positional unqualified close-keyword
Closes/Fixes/Resolves #Nliterals.