Episode 3 suggests to use git status before initializing a repo, but does not show that

[jdvorak001]

In a solution to a challenge in Episode 3 we say it would be good practice to check the status of the current directory just before issuing git init. But this practice is not actually shown in the lesson.

As a side-effect, the lesson actually introduces git status without being explicit about it.
I find this a bit underhands.

[jdvorak001]

And also, Episode 4 first uses git status in a context where it says "If we check the status of our project again".
I believe we should admit that we are introducing git status in Episode 3 already.

[Sipley]

I agree. The solution to "Places to Create Git Repositories" is a little confusing because the command git status doesn't give the output shown for the example as given. Suggestion: either move "if it looks like the following, you are good to go to create a new repository" earlier in the lesson when introducing git init or change to "if git status returns the following, it's best to avoid creating a new repository to be sure there is no conflicting repository in the directory". Alternatively, maybe combine the "Places to Create Git Repositories" and "Correcting git init Mistakes" sections, emphasizing the solution for the latter & highlighting the solution for the former as a useful tip?

[jdvorak001]

@Sipley, thanks for your comments. I suggested a solution to this issue in my pull request #686, which I have just updated with the latest gh-pages contents. Do you think the changes I suggested there could do the job, or should we try to refactor more?

[Sipley]

If I understood the changes correctly, yes! I think those are great!