News for hackers. Stuff that matters.
Re:Y U NO commit?? by blablabla123 on Monday October 20, 2014 @08:36AM (#8481765)
It's more of a workflow thing. When working on a difficult feature, or rather difficult ticket, that cannot reasonably split into 2, it makes sense to work on a separate feature branch. This branch is just for yourself and can be polluted with dirty commits. Once your done, your can git rebase the thing into one, beautiful commit.
Re:Y U NO commit?? by SargoDarya on Monday October 20, 2014 @08:44AM (#8481794)
If you're working in a feature branch I don't think it would be that much of a problem to be honest. Just be sure to squash the commits before writing the pull request later on.
Re:Y U NO commit?? by megablast on Monday October 20, 2014 @09:00AM (#8481870)
What do you mean by squashing the commits? Why would it matter if you do a pull request after committing a lot?
Re:Y U NO commit?? by ulisesrmzroche on Monday October 20, 2014 @10:50AM (#8482374)
You can squash or rebase history in Git, which basically means you compress all your changes into a single one. People use this to keep a clean history.