Repository navigation
fix: push where git push would, and skip branches it has no destination for - #19
Merged
Merged
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
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.
In diffnav,
clipboard-errorwas started fromupstream/main, the original author's repo, and tracks it.wt sync -ptook the branch's remote and rangit push --force-with-lease upstream clipboard-error, a force-push to someone else's repo. GitHub refused it this time (exit 128), but if you had write access there it would have gone through. Plaingit pushrefuses it: withpush.default=simpleand an upstream named differently, git has no single destination.Pushes now go where git's own
@{push}says, read for all branches with onefor-each-ref(%(push)and%(push:remotename)).%(push)still resolves when the remote branch was deleted, so the case where the remote branch is gone keeps pushing as before. A branch that has an upstream but no push destination is skipped with a hint, in the real run and in the dry-run plan:The same goes for a branch tracking
origin/mainunder another name, which used to get a new branch created on origin. Withpush.default=upstreamthe push now uses abranch:remote-branchrefspec, matching what git does. Branches without an upstream are still skipped silently.New
tests/push.rswith local bare remotes: a branch trackingupstream/mainis not pushed there while the normal one is, and a branch whose remote branch was deleted is still pushed.