Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocate directories and .gitkeep, Episode 4 to .gitignore in Ignoring Things, Episode 6 #687

Tammoo opened this issue Aug 20, 2019 · 1 comment


Copy link

Tammoo commented Aug 20, 2019

I'd like to suggest that Directories and .gitkeep at the very end of Episode 4 - Track Changes be relocated to the beginning of Episode 6 - Ignoring Things and have Episode 6 renamed to Keeping and Ignoring Things.

Here's my reasoning:
The Episode 4 section on directories and .gitkeep seem to come out of nowhere at the end of the episode and there really isn't any sort of strong explanation as to how .gitkeep is use to track empty directories or why one might want an empty directory. There is an example of how to set up a directory and add files to it using touch, but this is also confusing due to the files not having extensions. It seems that the file can be opened in nano, but not saved with an extension such as .txt. So, we end up having a spaceships directory with two files that appear to have unknown extensions. In Episode 5 directories and .gitkeep are not mentioned at all which seems to cause a bit of a disruption between the end of Episode 4 - directories and .gitkeep and all of Episode 6 - .gitignore. The flow might be better if directories and .gitkeep are a part of the conversation with .gitignore. .gitignore is not the opposite of .gitkeep, but I think their roles in relationship to directories and files, makes more sense if they are in the same episode.

Thanks so much.

Copy link

kpegion commented Sep 17, 2020

I agree. .gitignore and .gitkeep have not yet been introduced in the Lesson and seem to come from nowhere at the end of Episode 4. Up to this point Episode 4 flows very nicely and is easy to follow. Since the lesson is designed with a git novice as the target learner, I think these two files are introduced here in a way that could lead to confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants