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

Mallory Box
Mallory Box
1,111 Points
Posted by Mallory Box
Mallory Box
1,111 Points

When to use 'git commit -a -m'

I don't really understand when it is appropriate to use 'git commit -a -m' vs. just 'git commit -m'. I realize -a = all, but I don't understand why you would/wouldn't use this.

1 Answer

James Barnett
James Barnett
39,199 Points
James Barnett
James Barnett
39,199 Points

If you think the git add stage of the workflow is too cumbersome, Git allows you to skip that part with the -a option. This basically tells Git to run git add on any file that is "tracked" - that is, any file that was in your last commit and has been modified.

source: http://gitref.org/basic/#commit