Join the community!
Visit our GitHub or LinkedIn page to join the Tilburg Science Hub community, or check out our contributors' Hall of Fame!
Want to change something or add new content? Click the Contribute button!
Git will eventually become the long-term memory of your project, and you may decide to make the repository public so others can learn from or use your work.
Normally, versioning really is a good thing, unless…
- you accidentally stored sensitive information in your source code that you really do not want to be out in the public (e.g., API credentials, passwords),
- you accidentally stored files (e.g., large data sets, images) in your repository, that you cannot upload to GitHub (and hence can’t synchronize your repository anymore)
Luckily, there are ways out!
Simply undo your last commit
If you have just committed the file that you shouldn’t have committed, simply roll back to the last version of your repository.
git reset --soft HEAD~1
Entirely remove files
If you have committed sensitive data to your Git repository, use thef following resources to remove the file and all its previously issued commits.
- Navigate to your repository (i.e., the main directory of your repository), and open Git Bash.
- In Git Bash, type
git filter-branch --index-filter 'git rm --cached --ignore-unmatch file_to_remove' --prune-empty -- --all. Replace
file_to_removeby the path and file name of the file that you want to wipe out.
- If the command doesn’t work, verify you have used the correct file name and path name. Typically, the file name and path are indicated in a Git error message when trying to push or pull. Thanks to StackOverflow for this solution!
Check out the GitHub manuals for a step-by-step guide! Alternatively, use BFG Repo Cleaner, a convenient tool to remove unwanted files from your project.
Prevent committing specific files in the first place
Had to deal with removing sensitive information or unwanted files, and want to avoid making the same mistake twice?
Learn how to exclude files from versioning.