Elijah Newren

> The first commit that is singled out is rather recent: > > commit ac5213acbae8ab2e17589acc7c89b88b2d0e62ef (HEAD -> master, origin/master, origin/HEAD) Author: Pádraig Brady Date: Mon Sep 23 21:44:38 2024 +0100...

> > The fsck output didn't show any errors in any commits; it only pointed to errors in tags (unless there was more output from fsck that you didn't copy...

I'll go ahead and close out since the commands above clearly identified corrupt tag objects, and there's been no further questions. I will link to https://github.com/newren/git-filter-repo/blob/main/Documentation/examples-from-user-filed-issues.md#Handling-repository-corruption, though, as it may...

This is a very interesting idea. One possible big hangup... > Why not just display a message that explains what the tool will do and request a Y/N confirmation from...

Does applying this diff do what you want? ``` diff --git a/git-filter-repo b/git-filter-repo index 9cce52a..6c02d31 100755 --- a/git-filter-repo +++ b/git-filter-repo @@ -192,10 +192,10 @@ class PathQuoting: @staticmethod def enquote(unquoted_string): #...

Oh, cool, glad you found the needed change. I'm reticent to apply it as-is, though, because it'll likely slow things down for the general case (this function is called quite...

It sounds like you took a guess at what was taking up space and removed some files, but a lot of your space is in other files. Run `python $gfr...

Any chance you were using CMD to run your commands? If so, the problem may be that you used single quotes (`'`) instead of double quotes (`"`). If you changed...

Well, in that case, I'd suggest adding a `--debug` flag to your command so we can see what git-filter-repo actually saw; I have no idea if VScode did some weird...

No further response so I'll close out. I'm glad you found a solution. If you would like to dig further, feel free to reopen and provide the other bits of...