Added a guide to removing large files from repo history using bfg #249
Conversation
|
This is a good addition. The only thing I would add is a note that you may need to have Java working on your system before doing this. Is there any chance you can explain how to do it with git filter-branch, too? |
|
Currently working on a git-filter-branch implementation, and testing thoroughly. |
|
As I compare my git-filter-branch alternative to the sensitive data removal technique above, I notice that that subsection only removes the sensitive data from the latest commit, not all history. I'm going to finish this pull request with git-filter-branch instructions, but then the sensitive and large file removal sections should likely be merged. |
dustinfreeman
force-pushed
the
remove-big-files
branch
from
ea48d84
to
e3067b1
Compare
|
This is done, but pending acceptance of #269 |
dustinfreeman
force-pushed
the
remove-big-files
branch
from
5cf8711
to
6524bd1
Compare
…git-filter-branch explanation
dustinfreeman
force-pushed
the
remove-big-files
branch
from
6524bd1
to
4726abe
Compare
|
@deiga I've updated this PR on my fork with the latest from upstream master, including your #273 fix, but still have the old Travis CI error: I'm baffled. Is this TOC broken again? Is there some other way to read this error? Assistance appreciated. |
|
Yeah... I really don't care that much about the Travis error, if it is blocking us from having good content in here at all. I wouldn't worry about it. I'm going to merge this, because I think it's a useful addition. Good work. :) |
…8hudson#249) * Explanation of removing large files using bfg * doctoc applied to removing large files guide * Remove large files: clean up wording * Add subheadings to the large file removal section in preparation for git-filter-branch explanation * large file removal: clean up headings * large file removal: force push considerations note * Add word "private" to sensitive data section for searchability * Finish git-filter-branch instructions * Minor grammatical changes and simplifications.
…8hudson#249) * Explanation of removing large files using bfg * doctoc applied to removing large files guide * Remove large files: clean up wording * Add subheadings to the large file removal section in preparation for git-filter-branch explanation * large file removal: clean up headings * large file removal: force push considerations note * Add word "private" to sensitive data section for searchability * Finish git-filter-branch instructions * Minor grammatical changes and simplifications.
This guide requested in #207, and based on my own experience described in greater detail in this blog post
I have tested this empirically in my own huge private game development repo as mentioned in the blog post, and just re-tested this behaviour with bfg-1.13.0 and git 2.19.1. I have to admit I don't have a deep understanding of git's backend, and have never even used git reflog, so a review of what I'm doing here is welcome.