Release process fixes #4753
Merged
Release process fixes #4753
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
Readability down, working for PRs with no unique commits up
kmcgrady
approved these changes
May 23, 2022
AnOctopus
added a commit
that referenced
this pull request
May 26, 2022
* Don't commit RC bumps to release branch * Look up release PR a more robust way * Add script for creating release branch
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.
馃摎 Context
Additional fixes for problems found in our release process
What kind of change does this PR introduce?
馃 Description of Changes
Add a script for starting a release branch
Find the PR associated with a commit in a hopefully more reliable way
Skip committing RC build commits, getting the next version from pypi instead
馃И Testing Done