Let a found issue ride along in the card that found it #182
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!182
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-ride-alongs"
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?
Sessions can now fix an out-of-scope issue inside the card they are working, on the user's yes (asked each time), instead of sending it through the whole queue.
card.mjs ridefiles the issue as its own card in Backlog, with aRides with NEC-nmarker, the user's approval and a related link, and records it so the PR lists it ("Also fixes NEC-m").Changelog
NONE
Working cards keeps uncovering other issues, many of them one-line doc fixes. Each one went to Backlog and then, if queued, through a plan approval, a worktree, the gate, CI, the merge queue and main's run: far more than the fix. The user's decision (25 Sep 2026): offer to fix it inside the card being worked, asked each time and done only on a yes, and still record it as a card of its own, linked to the card it rode with, that reaches Done without a queue trip of its own. - card.mjs ride files the issue into Backlog, like create, with a "Rides with NEC-n" marker, the user's approval and a related link, and records it in the slot so the pull request lists it ("Also fixes"). - The merge queue moves a ride-along to Done in the same step as its parent, after main's run passes. On a bounce, a hold, a red main or a closed pull request it stays in Backlog, carrying its marker, because its fix is still in the parent's branch. - A ride-along is never claimed or queued: its work is already done. - The skill's out-of-scope question has three answers now: fix it here, Backlog, or Ready at a priority the user picks. The marker is what code reads, not the relation, since a relation can be edited by hand and a line in the body cannot drift from it unseen. Seven rules were each broken once to see their test fail, including ride-alongs reaching Done before main's run, and the marker matching mid-line. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015k9tkUtbU3wBpCHAHq7Qas