Repository navigation
yolo: archive only on Merge now when the answer starts a new run - #86
Merged
DocksDocks merged 1 commit intoOct 21, 2026
Conversation
…w run Landing step 11 now follows step 9 on Merge now and step 10 on any other answer. plan.mjs refuses to archive an open plan, so the old text failed on Leave pull request open. Refs #85
DocksDocks
deleted the
85-yolo-archive-only-on-merge-now-when-the-answer-starts-a-new-run
branch
October 21, 2026 21:36
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change fixes yolo Landing step 11. One message can answer the merge question and also start a new yolo run. In that case, the step said to archive and run Teardown even on
Leave pull request open. Then the issue stays open, andplan.mjs archiverefuses an open plan.Now step 11 follows step 9 on
Merge nowand step 10 on any other answer. Then it starts the new run. Code review of plan #83 found this problem (MEDIUM, rounds 1 and 2).Verification
node scripts/ci.mjs --plugin plan-lifecycle: all checks passed.Closes #85