I have a curious behaviour while running bfg-1.14.0 in that running the command
java -jar bfg-1.14.0.jar --convert-to-git-lfs '*.jar' --no-blob-protection <repo>
just returns the answer BFG aborting: No refs to update - no dirty commits found??
I'm trying to run this because I know that there is an installerCommons.jar present in the repo's history that is over 100MB in size. Sure, I'm gopher hunting with a tactical nuke by trying to convert all JAR files to LFS attachments instead of only the one that exceeds GitHub's transfer limits. I also happen to have one single DLL file in the same situation and '.dll' catches all* of the DLLs in the repository's history as expected. Plus, running the command with 'installerCommons.jar' explicitly instead of the wildcard does properly filter out this one file.
I have a curious behaviour while running
bfg-1.14.0
in that running the commandjava -jar bfg-1.14.0.jar --convert-to-git-lfs '*.jar' --no-blob-protection <repo>
just returns the answerBFG aborting: No refs to update - no dirty commits found??
I'm trying to run this because I know that there is an
installerCommons.jar
present in the repo's history that is over 100MB in size. Sure, I'm gopher hunting with a tactical nuke by trying to convert all JAR files to LFS attachments instead of only the one that exceeds GitHub's transfer limits. I also happen to have one single DLL file in the same situation and '.dll' catches all* of the DLLs in the repository's history as expected. Plus, running the command with 'installerCommons.jar' explicitly instead of the wildcard does properly filter out this one file.Why does '*.jar' not process anything?
This is in PowerShell 7 on Windows 10.