Automatic cherry-pick script #339
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #339 +/- ##
=======================================
Coverage 82.53% 82.53%
=======================================
Files 162 162
Lines 44043 44043
=======================================
Hits 36351 36351
Misses 7692 7692 Continue to review full report at Codecov.
|
alamb
force-pushed
the
alamb/cherry-pick-release
branch
from
1b98ebc to
a158774
Compare
8 tasks
|
I am going to merge this in and iterate on it in situ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
re #292
Rationale for this change
The idea from the New Releaes Process Proposal document is to make releases every other week from the
active_releasebranch but merge all new code changes tomasterThus we need a way to port changes that are "safe" for minor and patch releases to the active_release branch
What changes are included in this PR?
This PR proposes adding a
cherry-pick-pr.pyscript to automate the process of backporting / cherry-picking changes frommastertoactive_release.Example
I ran this script on a local copy of https://github.com/alamb/arrow-rs with the following commands, which created alamb#1
Next steps
I plan to run this script as a github action to automatically create proposed cherry-pick PRs for all commits to master. In the interim we can run it manually to create cherry-pick PRs for the
4.1.1/4.2.0release.Are there any user-facing changes?
No