Automate Intelligence Flow sync and verified releases - #25
Merged
Conversation
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
1 participant
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\n\nMake Intelligence Flow the only manual working repository while preserving Boatstack PR review, cross-platform CI, and tagged native releases.\n\n## What changes\n\n- authenticate cross-repository sync with the installed GitHub App\n- accept exact source commits and ignore stale dispatches\n- auto-merge only App-authored generated sync PRs after the full CI matrix passes\n- create the next patch tag only after successful main CI and only for release-bearing runtime changes\n- retain the six-hour scheduled sync as a fallback\n\n## Safety\n\nDocumentation-only syncs do not create binaries. The initial control-plane merge skips release creation until the projected runtime classifier arrives from Intelligence Flow.