4 ms·
The "Test Code Before You Commit" rule suggests that the writer does not distinguish between committing code and pushing code, between private changes and publi
by hughdbrown 13y ago
The "Test Code Before You Commit" rule suggests that the writer does not distinguish between committing code and pushing code, between private changes and public changes. When you commit changes locally, you can always rebase to your heart's content before pushing.
I think this says it best: "Treat public history as immutable, atomic, and easy to follow. Treat private history as disposable and malleable." https://sandofsky.com/blog/git-workflow.html https://sandofsky.com/blog/git-workflow.html
- jdludlow 13y ago"Test Code Before You Push" seems to be what they're trying to say.
- josephlord 13y agoI think as long as you are working on a feature branch you can even push it to the server. Better than locked up on your own machine and more robust to machine failure. I tend to push to at least two servers frequently (github or bitbucket and my own gitolite installation on a VPS). Obviously don't push to master or any shared mainline branch until it is done. When using github with others (even one other) I prefer to only merge to master with Pull requests so there is opportunity to review and comment on the code as a second pair of eyes.