-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Prepare for Merge Queue #17183
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
base: main
Are you sure you want to change the base?
Prepare for Merge Queue #17183
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,8 +50,38 @@ github: | |
main: | ||
required_pull_request_reviews: | ||
required_approving_review_count: 1 | ||
required_status_checks: | ||
strict: true # Require branches to be up to date before merging | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we not require up to date branches before we have enabled the merge queue? Otherwise that will slow down merging of PRs as we'll have a bottleneck / race for each PR that wants to merge Once there is an automated queue it makes sense because the queue handles the race |
||
contexts: | ||
- "Check License Header" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I worry about this list
I am particularly worried about the note in https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#branch-protection
![]() I think it is better to potentially have main fail some CI checks that we can fix rather than effectively locking ourselves out of committing anything |
||
- "cargo doc" | ||
- "build and run with wasm-pack" | ||
- "linux build test" | ||
- "cargo test (macos-aarch64)" | ||
- "Verify Vendored Code" | ||
- "Check cargo fmt" | ||
- "Verify MSRV (Min Supported Rust Version)" | ||
- "cargo check datafusion-common features" | ||
- "cargo check datafusion-substrait features" | ||
- "cargo check datafusion-proto features" | ||
- "cargo check datafusion features" | ||
- "cargo check datafusion-functions features" | ||
- "cargo test (amd64)" | ||
- "cargo examples (amd64)" | ||
- "cargo test doc (amd64)" | ||
- "verify benchmark results (amd64)" | ||
- "Run sqllogictest with Postgres runner" | ||
- "Run sqllogictest in Substrait round-trip mode" | ||
- "cargo test pyarrow (amd64)" | ||
- "clippy" | ||
- "check Cargo.toml formatting" | ||
- "Use prettier to check formatting of documents" | ||
- "check-files" | ||
- "cargo test datafusion-cli (amd64)" | ||
- "check configs.md and ***_functions.md is up-to-date" | ||
- "Process" | ||
# needs to be updated as part of the release process | ||
# Github doesn't support wildcard branch protection rules, only exact branch names | ||
# .asf.yaml doesn't support wildcard branch protection rules, only exact branch names | ||
# https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#branch-protection | ||
# Keeping set of protected branches for future releases | ||
# Meanwhile creating a prerelease script that will update the branch protection names | ||
|
@@ -122,6 +152,7 @@ github: | |
pull_requests: | ||
# enable updating head branches of pull requests | ||
allow_update_branch: true | ||
allow_auto_merge: true | ||
|
||
# publishes the content of the `asf-site` branch to | ||
# https://datafusion.apache.org/ | ||
|
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.
i wasn't able to check those via asf boxer (got a permission error on creating a new project). I checked other ASF projects so should be fine - but just in case I will take a look on the checks once this PR is merged