Why not instead (after backup-archiving the original repo.git directory) run the procedure on the git-origin server side (after backup-archiving the original, pre-bfg repo, of course)? Thus not requiring a push, and more importantly, keeping the origin server's repo completely clean of dirt--if I understand things correctly?
(When I ran the procedure from the client side and then pushed, my origin server repo.git still had all the past, uncleansed historical dirt. I then had to manually do some version of the above to clean it up.)
johnnyutahh
commented
4 years ago
The final step in the current (as of 2020-03-31) https://rtyley.github.io/bfg-repo-cleaner is a
git push.Why not instead (after backup-archiving the original
repo.gitdirectory) run the procedure on the git-origin server side (after backup-archiving the original, pre-bfgrepo, of course)? Thus not requiring a push, and more importantly, keeping the origin server's repo completely clean of dirt--if I understand things correctly?(When I ran the procedure from the client side and then pushed, my origin server
repo.gitstill had all the past, uncleansed historical dirt. I then had to manually do some version of the above to clean it up.)Am I missing something?