4 ms·
> which means git push will shout at you for being behind on branches you don't particularly care about right now. I think that behavior has been changed in re
by jrochkind1 12y ago
> which means git push will shout at you for being behind on branches you don't particularly care about right now.
I think that behavior has been changed in recent git, so by default it only pushes the branch you are on? (And the default is settable either way, even in slightly less recent versions).
But I can see some workflows git-up would be useful for. For me, not useful enough to deal with installing a plugin (with all that entails, including risk of bugs). Plus, while rebase is sometimes what you want, sometimes I really do want a pull, and the consequences of doing a rebase when you wanted a pull can be disastrous and hard to undo, and I'd be scared of a tool that defaulted to rebases everywhere.
- gizmo686 12y ago>the consequences of doing a rebase when you wanted a pull can be disastrous and hard to undo git reflog can easily rollback a rebase.
- jrochkind1 12y agoI realize it can be done, I generally don't find it easy, cause I have to remind myself how to do it, and it is a somewhat manual process of making sure you've found the right point to rollback to, etc. And of course, if you've made subsequent commits after the rebase but before you notice the mistake -- still can be done, but less and less easy. On the other hand, if you pull when you meant to rebase, that's somewhat easier and less error-prone to switch. For me anyway. ymmv.
- justinpaulson 12y agoYes, the default since git 2.0 is simple push which just pushes the branch you are on. It can also be set since I think git 1.8. I don't understand the issues that are being presented by this plugin and I really don't like the tone of the whole thing. If you understand push and pull the workflow is pretty simple, even in large groups.