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 trialDavid Hackett
3,191 PointsGIT... I'm being dumb ?!
Simple one- but my answer is wrong (matches the video I thought), what am I doing wrong ?!?!!
1 Answer
Chase Marchione
155,055 PointsHi David,
The challenges are aiming to get you used to the process of checking your repository's status, staging uncommitted changes, committing changes to the staging area, and checking your status to see that staging and committing occurred as expected.
1) To print the status of the current git repository: git status
2) To add the uncommitted changes to README.md to the staging area: git add README.md
3) To view the repository again: git status
4) To add the untracked file prototype.html to the staging area: git add prototype.html
5) To commit all changes made to the staging area: git commit -m "[Put your message here.]"
6) To check the repository once more: git status
-m is considered a flag, and it is used to add a message to your commit, so folks know what you committed.
Hope that helps!