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 Git Basics Getting Started With Git Staging Our Changes

Posted by Red Burke
Red Burke
2,677 Points

What's wrong with my code?

is this a glitch?

1 Answer

Chase Marchione
Chase Marchione
155,055 Points
Chase Marchione
Chase Marchione
155,055 Points

Hi Red,

Did you add the -m flag to your commit statement? The Treehouse compiler tries to instill the habit of adding messages to commits, which is good practice but easy to forget at first.

Task 1) git status

This checks the status of the current git repository (aka 'repo'.)

Task 2) git add README.md

This adds the uncommitted changes to the README.md file to the staging area.

Task 3) git status

The challenge wants us to view the repo again, so that we notice we now have changes to be committed.

Task 4) git add prototype.html

Now we're adding prototype.html to the staging area.

Task 5) git commit -m "Committing README.md and prototype.html changes."

We need the -m flag in order to add a message to our commit.

Task 6) git status

The challenge wants us to check our repo status one more time, so that we notice that there is nothing more to commit.

Hope this helps!