Repository navigation
Revert the ship-signal requirement for unmerged work (#52) - #56
Merged
Merged
Conversation
- Count a PR or ticket as pending again, since capture runs before a PR usually exists - Drop the closing-note line for skips caused by a missing ship signal
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 runs in the turn where a finding happens, and on a feature branch that is almost always before a PR exists. Requiring a PR or an explicit "this will ship" therefore skipped most learnings about branch work, and the closing-note prompt to supply the signal never led to a second capture.
This restores the earlier rule: a PR or ticket is enough to save unmerged work as pending. Memories from branches that never merge are left to memory-audit, which already drops pending work with no matching branch or PR, while a memory that shipped differently is now corrected by capture itself (#51).
Test plan
mcs sync, then on a ticket branch with no PR find a cause in new code and run continuous-learning → expect a memory with a**Pending:**line naming the ticketPending:, as before