Currently, cloning the repo can be quite slow. This is probably because of the Python bytecode blobs that were originally added (but later removed). As these are still in the commit history, the repo is still bloated. Using something like BFG you could remove all the remnants of both the *.pyc and the .DS_Store files. As this repo is unlikely to get large code-based external PRs, rewriting history shouldn't have an effect on others. Note that BFG doesn't clean the HEAD commit but all commits before it so there would need to be a non-ignored-removing commit before using it.
Blocked by #3
Currently, cloning the repo can be quite slow. This is probably because of the Python bytecode blobs that were originally added (but later removed). As these are still in the commit history, the repo is still bloated. Using something like BFG you could remove all the remnants of both the
*.pyc
and the.DS_Store
files. As this repo is unlikely to get large code-based external PRs, rewriting history shouldn't have an effect on others. Note that BFG doesn't clean the HEAD commit but all commits before it so there would need to be a non-ignored-removing commit before using it.Example:
After doing this it is recommended to delete your other (previous) clones and run
git clone
again.