githug VS bfg-repo-cleaner

2) Run through this little game.

Real talk, the first 3 chapters of this book and this learning game will teach you everything you need to know and put you miles ahead of the average developer.

Gameified learning experience => https://github.com/Gazler/githug

If you're new to programming, read the first 3 chapters of this book and then complete this little game. Do this and you'll be better at git than--no joke--90% of programmers (especially the people in this thread, holy shit).

If you're not as comfortable with git as you'd like to be, I highly recommend the first three chapters of this free book, written by the creators of GitHub. (The other chapters are excellently written as well, it's just that the content isn't your bread-and-butter.) Also, use this quick, free game to practice.

The tool to make your life 100x easier (and safer!) is RIGHT THERE. Read the first 3 chapters of this free book, then try this game. Don't reinvent the wheel and make it square in the process.

I like this interactive game. You can use command line to solve git problems: https://github.com/Gazler/githug

So, this is a PSA that you can't simply delete the file and commit that. You must either use a tool like BFG Repo Cleaner which can scrub files out of your commit history or you could simply delete your repository and recreate it (easier, but you lose your commit history).

It shouldn't take a lot of time to modify. There is even a tool just for this scenario https://rtyley.github.io/bfg-repo-cleaner/

You need to git out the BFG: https://rtyley.github.io/bfg-repo-cleaner/

This method requires changes to be committed as usual in the regular project repository, and then committed again in the -docs repository. This is inelegant, but it provides clear distinction between private and public content. You cannot publish your regular repository without using git-filter-branch or some Git history rewriting software like BFG Repo-Cleaner. This would rewrite every commit in the history of the repo, removing all changes to the paths you don't wish to publish. This would change all the commit hashes and possibly other metadata – in short, it wouldn't be the same repository.

GFG Repo-Cleaner

You could use a repo filtering tool (e.g. BFG Repo-Cleaner) to clean up unintended information leak from your Git repository -- which retains the history timeline, but I believe it would rehash all the commits and render everything unsigned, which is probably not the desired outcome.