Adding an objective covered in the lesson

[catsmith]

git status seems to me an important and useful enough command to be included in the lesson objectives.

[munkm]

@catsmith I think this is a great addition to the objectives of this lesson. It's also helpful for future lessons, so really emphasizing it in the lesson where it's introduced is a good idea. However, lesson 04 heavily emphasizes git status too, and the questions and keypoints in that lesson are "How do I check the status of my version control repository?" and "git status shows the status of a repository." , respectively. Maybe you could modify your keypoint here to be "Introduce how to check the status of a local Git repository."? What do you think?

I think it might also be nice to update the question relating to git status in lesson 04 to reflect this too. Lesson 04 really shows how powerful git status is in checking our repository (and how it changes as we add and commit files), but since it is introduced in lesson 03 we may want to reword it slightly. I'd update it to something like "How does git status change as I make changes in my version control repository?".

[munkm]

Hi @catsmith would you like any help updating these objectives slightly? I'm happy to help if you need it.

[emcaulay]

Thank you @catsmith , for your contribution! I agree with you that "git status" is one of the most important takeaways for the whole git lesson! Very important to make sure we highlight it as either an objective or key point.

However, when I am reviewing the episode 3 today, I don't see any use of "git status" in this episode. I think this pull request has become outdated. It doesn't seem to be the right objective for the content of episode 3.

That being said, it's easy for me to get confused so I might be looking at the wrong thing!

[kekoziar]

this objective was subsequently added to Episode 4, which in depth uses git status. Closing.