Clarify to not commit proposed change

[lexnederbragt]

A learner missed this and had already committed the change before testing git checkout. This change intends to help avoid this mistake.

[kekoziar]

@lexnederbragt Having the challenge written in such a way that a learner never misses it, defeats the purpose of the challenge. Did they miss it because it's unclear, or because the learner didn't quite grasp the difference between a change being staged and committed? I'd rather not write in such a way that it takes into account each mistake a learner might make.

That said, this would probably be best clarified with a solution to the challenge. Are you willing to write up a good solution instead, taking into consideration the common mistakes learners might make with this?

[lexnederbragt]

I see your point and agree that my change would be making the challenge less, well, challenging.
I like the idea of adding a solution and will submit one soon.

[lexnederbragt]

PR updated with a proposed solution. Please review!

[kekoziar]

What version git are you running? My version is prompting with git restore not git checkout

[lexnederbragt]

I agree that recent versions of git use git restore to restore files instead of git checkout. However, the lesson is based on older versions of git, and uses git checkout. So, this PR needs to use the current lessons convention.

See also discussion in #691 on updating the git lesson to version of git that uses git restore (and git switch).

[kekoziar]

Looks good. I made some minor changes to make the input/output in the solution standardized with the rest of the lesson, and added clarification in the challenge prompt.

Thank you for submitting this solution!