Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Bethany Cooksey14,242 Points
How often do you recommend staging and committing your changes?
So I was wondering how often most developers stage and commit their new changes, because it seems that it could get very tedious very quickly.
Do you really recommend doing this for each little change so you can properly track your changes, or is it okay to just gauge whether or not a change is important enough?
And if so, do you have any helpful tips for gauging if a change is important enough to add and commit it?
That's a lot of questions, sorry. :)
Steven Parker210,442 Points
Organizations often have rules about when things must be submitted, but when none apply I generally only check in a completed change order that builds correctly and has been at least unit tested. Or in the absence of a change order, anything that affects the program operation or the UX (also when complete and tested).