Repository navigation
Require a ship signal before capture saves unmerged work - #52
Merged
bguidolim merged 1 commit intoOct 28, 2026
Merged
Conversation
- Count only a PR or the user saying the work will ship as pending; a ticket alone no longer does - Apply the same signal to decisions about code the default branch does not have yet - Name skips caused by a missing ship signal in capture's one-line note
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.
Why
Capture saved memories from PoCs and investigations whose branches never merge. Any ticket counted as proof the work was in flight, every branch carries one, and a decision about code that doesn't exist yet has nothing to grep, so neither check held anything back.
Now unmerged work is saved only with a PR the session created or the user named, or the user saying the work will ship. That applies to decisions about code the default branch doesn't have yet, too. Findings about code already on the default branch are saved as before. Anything held back is named in capture's closing note, so the user can supply the signal.
Stacked on #51; merge that first.
Test plan
mcs sync, then on a ticket branch with no PR settle a direction and run continuous-learning → expect a skip and the "say if this will ship" note**Pending:**line