ci: run build.yaml on vnext#2068
Open
tyrielv wants to merge 1 commit into
Open
Conversation
Add `vnext` to build.yaml's pull_request/push branch filters so the feature-integration branch gets the same CI (build + unit + functional tests) as master. This lets PRs targeting vnext produce the required status checks. Assisted-by: Claude Opus 4.8 Signed-off-by: Tyrie Vella <tyrielv@gmail.com>
tyrielv
force-pushed
the
tyrielv/vnext-ci-triggers
branch
from
July 20, 2026 14:57
ab2b111 to
72ef651
Compare
tyrielv
changed the title
tyrielv
enabled auto-merge
July 20, 2026 14:59
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
Adds
vnexttobuild.yaml'spull_request/pushbranch filters so PRs targeting thevnextfeature-integration branch run the same CI as master (build + unit + functional tests) and produce the required status checks.Why
Branch model:
masterstays the shippable line (stabilization / bug-fixes; releases cut here);vnextaccumulates next major/minor feature work until it's promoted to master via a normal reviewed PR.Without this, PRs into
vnextwould produce no check runs and be un-mergeable oncevnextis branch-protected to mirror master's required checks.Follow-ups (admin, not in this PR)
vnextruleset mirroring master's policy (1 approval + code-owner + required CI checksValidationandBuild, Unit and Functional Tests Successful, block force-push/deletion).Not included
vnextwill be done manually via normal reviewed merges instead.