Repository navigation
fix(harness): ship gate tracks only issues a merged PR closes (0.3.3) - #35
Merged
Merged
Conversation
…/Fixes/Resolves); bare references are a toast (0.3.3)
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.
The ship gate demanded a Done transition for every issue ID a merged PR named that had appeared in the session, including umbrella issues named only as context ("Refs AUD-2209", a program ID in a squash subject) and issues already Done. On 2026-11-07 that blocked every stop for a whole session.
Now only IDs after a closing keyword (Closes/Fixes/Resolves, with optional colon and comma/and/& lists) are tracked; other named IDs get the existing toast.
closingIds()in harness/hooks/ship-gate.tsscripts/ci.sh: marketplace and 5 mods passed (harness 165 pass, 0 fail).