bzr push should default to parent branch if that's writable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Breezy |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Here's a very common work flow:
bzr branch lp:something
cd something
hack
bzr commit
bzr push
bzr decides to be unhelpful, and the "bzr push" fails.
I think it's not unreasonable for this to at least *try* to push to the parent branch; if that fails, then sure, say no push location defined. If you own the branch, it's very likely that it's the branch you meant to push to.
(Ubuntu developers follow this work flow every time they hack on a package for example)
Another obvious solution, if changing push isn't possible, would be to set the push location at branch-time if the branch was writable - the lp plugin at least knows that, and I'm sure the other URLs (bzr+ssh for example) tell you whether it's writable or not
tags: | added: easy |
tags: | removed: easy |
tags: | added: check-for-breezy |
tags: |
added: location-ui removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
I'm not sure that would be a safe default for all workflows but it's an interesting suggestion.
As a workaround you should be able to do 'bzr push --remember :parent'.
See also bug 538887.