- 
                Notifications
    You must be signed in to change notification settings 
- Fork 109
chore: add test-ci branch protection rules #3937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR sets up branch protection rules for a new test-ci branch to enable testing of CI configurations without affecting the main branch. The changes establish the same protection requirements as the main branch while allowing for safe experimentation.
- Added branch protection configuration for test-cibranch
- Configured required status checks including GUI, core, and Python UDF tests
- Set up pull request review requirements with single approval needed
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| LGTM! | 
### What changes were proposed in this PR? This PR adds the following CI with new names: - `core` -> `scala`, currently contains all scala tests for multiple packages/services, we could do more separation and renaming later. - `gui` -> `frontend`, that is consistent to our repo directory rename. - `python_udf` -> `python`, to simplify and re-purpose, because it contains tests for entire python engine (although a main part is to support UDF). Note that we will remove the old CIs in another PR. ### Any related issues, documentation, discussions? work related to #3939 ### How was this PR tested? Manually tested with #3937. ### Was this PR authored or co-authored using generative AI tooling? No.
### What changes were proposed in this PR? This PR cleans up the left over changes from CI updates: 1. it removes the old CI runs (caused by #3941). 2. it removes the rules against `test-ci` branch (introduced by #3937 for testing purposes). ### Any related issues, documentation, discussions? finishes and resolves #3939 ### How was this PR tested? Manually tested. ### Was this PR authored or co-authored using generative AI tooling? No.
What changes were proposed in this PR?
This PR is the initial setup for testing #3934. We create a new branch
test-ciand add the branch protection rules againsttest-cifor testing purposes.The rules names are exact string matches from Github Actions.
Any related issues, documentation, discussions?
related to #3934
How was this PR tested?
N/A. It should not affect any other branches. We are manually testing.
Was this PR authored or co-authored using generative AI tooling?
No.