chore(ci): explicitly declare main branch's CI rules #3938
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
There was a problem hiding this comment.
Pull Request Overview
This PR explicitly declares CI rules for the main branch by adding required status check contexts to the branch protection settings. The changes ensure that specific CI checks must pass before merging into the main branch.
- Adds required status check contexts for the main branch protection rules
- Specifies GUI tests across multiple platforms and Node.js versions
- Includes core, Python UDF tests, and validation checks as required contexts
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 changes were proposed in this PR?
This PR explicitly declares the CI rules on
mainbranch.Any related issues, documentation, discussions?
resolves #3934
How was this PR tested?
Tested with
test-cibranch before. Now merging rules tomain.Was this PR authored or co-authored using generative AI tooling?
No.