Update CI rules #1188
Merged
Update CI rules #1188
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
… committer approval. This matches the arrow-rs repo.
alamb
approved these changes
Jul 15, 2025
There was a problem hiding this comment.
I think given the maintainer bandwidth available and the fact that any release has a three day voting / review period, this change will accelerate development without meaningfully reducing oversight
If we get to the point where there are many more commiters to datafusion-python who are able to do timely reviews and want to ensure additional oversight we can revisit
Thank you @timsaucer for driving this forward
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.
Which issue does this PR close?
None
Rationale for this change
This PR copies the configuration of the
arrow-rsrepository. It does not require a committer to sign off on every PR but it does require that all branches are up to date. This is based on a discussion with another PMC member about the speed of development in this repository. The goal is to balance having some protection on the main branch and also allowing work to not be held up.What changes are included in this PR?
Update asf.yaml file.
Are there any user-facing changes?
None