fix(changelog): the twins fragment needs an issue reference (#1112) #1156
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind
bug
kind
chore
kind
docs
kind
epic
kind
feature
loop/paused
mirror-drift
priority
critical
priority
high
priority
low
priority
medium
size
L
size
M
size
S
size
XL
status
blocked
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
frankenbit/release-toolkit!1156
Loading…
Reference in a new issue
No description provided.
Delete branch "i/1112-twins-fragment-issue-ref"
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?
fragment-checkrequires an issue reference in the summary line. The fragment I added in #1155 has none, so main went red the moment #1155 merged, and every open PR inherits it.That is how it surfaced — on #1154's
toolkit-self gate (PR's own rt), not on its own. #1154's content is unaffected; it is failing on a file it does not touch.Mine, and #1155 should not have merged without it. One token added.
Verified against main's own
rt:1 fragment(s) lack an issue reference→ 0, density PASS, rc=0.🤖 Generated with Claude Code
https://claude.ai/code/session_01LUEggQMJjaizj2nFVofeyH