Add rough cut of 'blobbase' #712
Open
+17
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Like interactive rebase for blobs Signed-off-by: Stuart MacDonald <stuartm.coding@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a rough draft for a "blobbase" feature. It operates like git's interactive rebase but is not interactive. I'm not intending for this to be merged; just looking for comments on whether this could be merged. It would need test cases at least.
After running
git-filter-repo --analyze, one annotates the resulting.git/filter-repo/analysis/blob-shas-and-paths.txtwith commands and feeds that back in viagit-filter-repo --blobbase. This avoids most of the human error inherent in a person transforming ablob-shas-and-paths.txtinto a file that--strip-blobs-with-idscan handle.The new process leaves the paths in place making blob selection easier.
It is a process that most git users will already be familiar with from rebase.
Unless the extra line in the
blob-shas-and-paths.txtfile causes issues, this is 100% backwards compatible.I am currently using this to clean a repo that had a lot of build artifacts checked in. I find it better than (re-)creating a blob-sha-only file from
blob-shas-and-paths.txtbecause I can see what I'm selecting and it's less transformation than making the blobs-only file.Part of my equation is this lets me do the annotation slowly over time/many iterations while I figure out what needs to come out and what stays.
Original commit message:
Like interactive rebase for blobs