3 ms·
There's a reason commit and push are two separate actions. That said, most people commit+push in the same keystroke. git revert is my best friend.
by bkanber 6y ago
There's a reason commit and push are two separate actions. That said, most people commit+push in the same keystroke.
git revert is my best friend.
- Waterluvian 6y agoWhat is the reason? Like are people just not pushing changes to remote branches? Or is there some value in stuff to do in the small time between commit and push? Like are you checking your work before pushing?
- pirocks 6y agoIn the past I've done stuff like not pushing until the end of the day/coding session. Usually though I just end up committing and pushing immediately and then realizing I need to amend something and make a note to rebase later(I totally always do that rebase /s).
- dec0dedab0de 6y agoI try to keep my commits small, and I don't push each time because I have a Jenkins pipeline thats going to update a server for my branch and run unit tests and all that
- triceratops 6y agoIntermediate commits. For example, while building a UI - HTML is done, but you haven't begun styling. You want to be able to revert to a good point in case you screw up, but there isn't much reason to push it to a remote because it's not a shippable state. As long as your computer is being backed up (you are using backups, right?) you won't lose any data by not pushing to a remote.