You can push up a series of commits, but each one is it's own code review so you want to do it less often. Another thing is if you have to add something to the HEAD^^ you have to rearrange your history and squash things together, but in the end the history is really clean. Also, each push of of each commit is versioned so you can easily tell what has changed between the last code review and the current; this is impossible with GitHub if you want to keep your history clean and compare different versions of the code review.
HN user
ymmy
5 karma
Posts0
Comments4
No posts found.
Abandoning Gitflow and GitHub in favour of Gerrit 10 years ago
Just what we need. Another package manager. 12 years ago
Fine, don't use it. But you probably will because after fighting it you will likely find it makes you life easier.
Amazon was down 13 years ago
The console is working if you are already logged in. Although loggin requires going through www.amazon.com.
MongoDB lessons 14 years ago
Asynchronous driver isn't always needed, but he was working with Tornado, an asynchronous framework. Using anything non asynchronous that has the possibility to block for any significant period of time (i.e. network call or database call) with tornado defeats the whole purpose. Hardly MongoDB's fault.