You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What i did:
git-filter-repo --analyze
Prepared the path-deleted-files.txt
and after run: git-filter-repo --invert-paths --paths-from-file ./path-deleted.txt
Everything worked fine and the tool did his job, but for my surprise after i faced some issues.
There was java classes completely deleted,and i cannot even build it. I could go through and remove the classes that i would like to keep from the list, but im wondering, since these classes still existing, why are removed?
Is there any flag that i can use, so the tool will not remove files that existing in Head, but only the previous versions?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What i did:
git-filter-repo --analyze
Prepared the path-deleted-files.txt
and after run: git-filter-repo --invert-paths --paths-from-file ./path-deleted.txt
Everything worked fine and the tool did his job, but for my surprise after i faced some issues.
There was java classes completely deleted,and i cannot even build it. I could go through and remove the classes that i would like to keep from the list, but im wondering, since these classes still existing, why are removed?
Is there any flag that i can use, so the tool will not remove files that existing in Head, but only the previous versions?
Beta Was this translation helpful? Give feedback.
All reactions