Issues: newren/git-filter-repo
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Turns out my assumption was wrong:
git lfs migrate export --everything --include="*"
does rewrite the whole history, across all branches, reinjecting all the large files' consecutive versions ([see here](https://github.com/git-lfs/git-lfs/issues/910#issuecomment-551566315)). Awesome!
#555
opened Apr 10, 2024 by
cklim033
Test suite succedes with Python 3.11 but has multiple failures with Python 3.12
#554
opened Apr 10, 2024 by
alerque
Question: Recommended way to log the usage of git filter-repo and related changes?
#548
opened Mar 12, 2024 by
jeswcollins
minor: Logic error with
_commits_referenced_but_removed
on a GitHub Gist web url in commit message 😂
#545
opened Feb 23, 2024 by
Challanger524
remark: Pity that this tool can't run scripts/programs and it is not clearly stated
#544
opened Feb 23, 2024 by
Challanger524
Renaming paths into pre-existing path causes double-nested paths (sometimes)
#538
opened Jan 29, 2024 by
ChrisCarini
Remove a commit based on its message content or filename with git filter-repo --commit-callback
#534
opened Jan 7, 2024 by
tomdev92
git filter-repo --invert-paths --path <directory/file> creating duplicate branches
#530
opened Dec 19, 2023 by
Bharath0601
Previous Next
ProTip!
Follow long discussions with comments:>50.