Sync Boatstack from Intelligence Flow Labs @ 5850912e0d94 - #147
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 28, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-5850912e0d94
branch
July 28, 2026 16:45
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.
What this sync releases
You can now wait for a pull request to move without polling it yourself
flow watchobserves your delivery frontier on an interval and exits the moment something changes: checks finish or fail, a review lands, a merge happens. It also exits immediately when nothing can move, and with a distinct exit code when its timeout passes with no change, so a script or an agent loop can tell "something happened" from "still waiting". Defaults are a 30-second interval and a 30-minute timeout, both adjustable.The watch only observes: it performs no writes and never runs an operation on your behalf. When it exits, run
next-statusand continue from the fresh state. Before this, waiting on CI meant either re-running status by hand or asking your agent to poll GitHub in prose.Projection provenance
Generated from
operatorstack/intelligence-flow@5850912e0d947f9fbee5048d9ed6a79a5d614ff1.Review provenance, tests, and examples before merging.