Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Development Tools Introduction to Git First Commits Viewing Changes to a File

Bethany Cooksey
Bethany Cooksey
14,242 Points
Posted by Bethany Cooksey
Bethany Cooksey
14,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. :)

1 Answer

Steven Parker
Steven Parker
229,744 Points
Steven Parker
Steven Parker
229,744 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).