I am currently migrating our source from perforce to git via GitFusion. Somehow it is not working for me to exclude certain paths from git. Even though I specify an exclusion on the view, the files end up in the Git history. I need to exclude some test file directories as they exceed some file size limitations.
My p4gf_config looks like this:
[@repo] description = MyProduct repository [master] git-branch-name = master view = //depot/MyProduct/Trunk/... ... -//depot/MyProduct/Trunk/src/Module1.Tests/TestFiles/... src/Module1.Tests/TestFiles/... -//depot/MyProduct/Trunk/src/Module2.Tests/TestFiles/... src/Module2.Tests/TestFiles/... -//depot/MyProduct/Trunk/src/IntegrationTests/TestFiles/... src/IntegrationTests/TestFiles/... [release7.3] git-branch-name = release/7.3 view = //depot/MyProduct/Release7.3/... ... -//depot/MyProduct/Release7.3/src/Module1.Tests/TestFiles/... src/Module1.Tests/TestFiles/... -//depot/MyProduct/Release7.3/src/Module2.Tests/TestFiles/... src/Module2.Tests/TestFiles/... -//depot/MyProduct/Release7.3/src/IntegrationTests/TestFiles/... src/IntegrationTests/TestFiles/...
The syntax itself is detected as valid. I could see that git fusion even updated/reordered some of the remove records after I ran p4gf_init_repo.py on the server. But when I make a clone afterwards and scan for big files I can still see files from the excluded paths.
Is it possible that they are included back due to some merge/branching that happened in Perforce? Can I get rid of them otherwise? I would like to avoid cleaning the git repository manually (filter-branch, bfg + gc) as I saw the operations are very time consuming.