chore: scripts/ and hooks/ headers still cite bare issue numbers #737
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#737
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Context
The danglingref check resolves every issue/PR reference in shipped surfaces against the forge. In CLI help and tool descriptions the remaining references are usage examples (
open issue #42,mark PR #5 ready) - fine.The operator scripts under
scripts/and the plugin's hook scripts underhooks/scripts/still carry bare issue-number citations in their header comments: the issue that motivated a check, a forge-VM header naming the gate-step issue, a hook comment citing a rule's issue. These resolve today, so the check passes them; they are not usage examples, and the hooks ship to plugin users.Ask
Remove the bare issue numbers from those headers, preserving each sentence's meaning. Follow-up; it does not block the danglingref change, because the citations resolve.