ci: run build.yaml on vnext and auto-sync master into vnext#2068
Open
tyrielv wants to merge 1 commit into
Open
ci: run build.yaml on vnext and auto-sync master into vnext#2068tyrielv wants to merge 1 commit into
tyrielv wants to merge 1 commit into
Conversation
Add `vnext` to build.yaml's pull_request/push branch filters so the feature-integration branch gets the same CI as master, and add a workflow that keeps vnext current by merging master into it. The sync is one-way (master -> vnext, no review); vnext -> master promotion stays a reviewed PR. The sync job authenticates as the identity listed in vnext's ruleset bypass list via the VNEXT_SYNC_TOKEN secret, and files an issue on merge conflict. Assisted-by: Claude Opus 4.8 Signed-off-by: Tyrie Vella <tyrielv@gmail.com>
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.
What
Prepares CI for the upcoming
vnextfeature-integration branch:vnexttobuild.yaml'spull_request/pushbranch filters so vnext PRs get the same CI as master..github/workflows/sync-master-to-vnext.yaml— a one-way workflow that keepsvnextcurrent by mergingmasterinto it on every master push (plus an hourly safety net). It files an issue on conflict.Why
Branch model:
masterstays the shippable line (stabilization / bug-fixes; releases cut here);vnextaccumulates next major/minor feature work. master -> vnext flows automatically (already-reviewed code); vnext -> master promotion stays a normal reviewed PR.Follow-ups (admin, not in this PR)
vnextbranch.vnextruleset mirroring master's policy, with the sync identity on its bypass list.VNEXT_SYNC_TOKENsecret (the sync identity's token).The sync workflow no-ops until
vnextexists, so merging this PR is safe on its own.