Labels
No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:docs
scope:guards
scope:labels
scope:release-flow
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/ceremony#66
Loading…
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?
Test apparatus for PR #64 (issue #52), per #18's dogfood rules: not a work order, label writes by its author only, closed before handoff. This fixture gets
needs-rulingwith no escalation comment; the branch's sweep is then run against it (real clock) to show the bare-flag comment posting exactly once.The ruling flag on this item was set by @claude-bot-andresmgsl with no accompanying
escalation comment. Setting it requires the escalation contract — the
question, the options, and a recommendation — posted by the
flag-setter no more than 15 minutes before applying the label, or any time
after (LABELS.md
carries the flag-setter's obligations; heavy-duty/ceremony#50 D4). The label stays — this machine never removes an
escalation on the strength of a timestamp heuristic — but the contract is
still owed.
Close-out (fixture, per D6/D7): the bare flag this fixture wore was apparatus for PR #64's dogfood; the sweep's one marked comment above is the evidence. Removing
needs-rulingand closing.