5 ms·

I predict this will happen a LOT more often with git 2.0 changing the default push behavior to pushing all branches. If you've ever --force pushed over a tempo

by Groxx 13y ago

I predict this will happen a LOT more often with git 2.0 changing the default push behavior to pushing all branches. If you've ever --force pushed over a temporary remote branch (e.g. to show something to a coworker), 2.0 will run the risk of overriding everything. Hooray!

0x0 13y ago
Isn't the new git2 default to only push the currently checked out branch?
- tacticus 13y ago
  yes but only if there is a same named branch on the remote end. i kinda prefer the upstream (names can be different but i set up an explicit link) option to simple
Axsuul 13y ago
Don't you mean it will happen less often? Git default push behavior in 2.0 will be 'simple'.
- emn13 13y ago
  But these were lots of repos and not just forks, but the look of it - If that's the case, I'm guessing some scripting was involved, so the defaults wouldn't have mattered.
- Groxx 13y ago
  /me rereads a blog post or two weird. I had that backwards. oh well, thanks all, I was wrong :)