+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Coders Lounge (https://hackforums.net/forumdisplay.php?fid=5)
+---- Thread: How often do you commit? (/showthread.php?tid=4313327)
How often do you commit? - ASLR - Jun 29, 2014
I see some people make commits with like 500 changes in one commit, meanwhile I commit after most changes and have tons of commits. So for those of you who use some form of git repository when coding, how often do you commit?
* - ѕнα∂σω - Jun 29, 2014
I personally commit after I write another functional piece of code. I usually write a function/method (or a few of them, if they go hand in hand), test it, then commit. I tend to push my code after every commit as well.
* - Crake - Jun 29, 2014
I commit every code block revision. So, if I add a new major block, I commit. If I revise it, I commit. I try to isolate it to one block at a time for easier rollbacks.
* - Pillows - Jun 29, 2014
I commit whenever I finish a piece of code that works. Or whenever I need to fix a bug.
* - EmptyRedData - Jun 29, 2014
I commit on bug fixes and feature additions. I should commit more, but I just feel like anything too small is cluttering up the commit history. I dunno.
* - NeoXiD - Jun 29, 2014
I always commit when new functionality was added, some bug was fixed or something else has changed. Yes, this will result in hundreds of commits within big projects, but this is actually how Git should be used.
In the past, I sometimes made one commit for each new version, but that's really not a good idea. Also, when working within a team, small and comprehensible commits are important.