aide-close

Topics in the source

• A project with a board
• Workflow
• Step 1 of 4: Move the spec to the archive as closed
• Step 2 of 4: Commit
• Step 3 of 4: Confirm
• Step 4 of 4: Merge into main

Close a spec that turned out not to work: stamp the reason, move it to archive/, and let the code branch it never used be deleted rather than merged. Input: $ARGUMENTS (a spec number, a full folder ID, or an issue key its title began with, plus the reason the user closing it typed) Working interactively, hand the step to the board first: Ask for the reason first when none was given. Exit 3, or no such command: go on with Step 1. Any other exit: its output is your last words; do nothing else. -- The steps below are this skill's own, inside the queue's close step. Mark each one in the log, so a reader can follow the run: when it starts, write one line --- Step N of X: — started, and when it ends, one line --- Step N of X: — done. A step that ends the run early says — stopped: in place of — done, and one that does not apply to this run — skipped: . Step 4, the merge into the default branch, is Aide's, after this session: Aide writes its marks, and the close is finished only when it is done. First write --- Step 1 of 4: Move the spec to the archive as closed — started, and when this step ends, --- Step 1 of 4: Move the spec to the archive as closed — done. A script resolves the argumen

This is an excerpt. Refer to the complete source and its current requirements.