feat: avoid pushing release branch only for rebasing #114
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
apricote
force-pushed
the
push-when-changes
branch
from
3938c7a
to
f94c8f4
Compare
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.
Right now releaser-pleaser pushes the branch even if it is only for a "rebase", this wastes CI resources. Instead it should only push when there are changes to the files it owns.
Old: Push when there is a diff
origin/release-pr..release-prNew: Push when the these two diffs are not the same:
origin/main..release-pr$(git merge-base origin/main origin/release-pr)..release-prCloses #92
Right now the tests are still WIP. I was able to salvage the git test framework from a0a064d#diff-483ac1310305711011d4ac806cabfaacb53b40c182ddcd7f251b2cd141e3e229