bfg is not always perfect

When something broken in your git lfs workflow

It is awful when this happened in your packaging procedure. Image that, everything should have been a binary archive being end in a text point file in your installation media.. Nightmare..

So how could it happen?

All begins with a repo optimization..

You have a repo full of binary files, and you want it to be clean and neat.

You know that bfg will help you on the job. And did the convention with some magic file pattern like *.{jpg,png,zip,gz,tar}

Then you replaced the repo, without any sanity test.

Git lfs pointer files begins to show up in your source tree

You got this after every git operation, as the git hooks did not work as expected.

They don’t understand bfg generated filter rules in your .gitattribute file.

Git lfs files shows as modfied after git lfs pull

You know that git lfs pull can help you with pointer file => binary convertion.

But it do not help much, as everything converted shows up as modfied in git status, as the git hooks did not work as expected.

They don’t understand bfg generated filter rules in your .gitattribute file.

Way to rescue

Run bfg with one type of file a time, until all kind of binary files are covered. e.g.

For pattern *.{jpg,png,zip,gz,tar} previous mentioned. Run bfg five times, for each time with only one filetype (suffix).

Refer: https://support.atlassian.com/bitbucket-cloud/docs/use-bfg-to-migrate-a-repo-to-git-lfs/ Refer: https://github.com/rtyley/bfg-repo-cleaner/issues/116