Elijah Newren

I've got a guess at what might be causing this and the fix. Could you try with the proposed fix over at https://github.com/newren/git-filter-repo/commit/b4391762a6ebfd3c65e25a9eac35aac36e06cf3b ?

I'll look forward to your example repo, but it's possible I can help a little based off your descriptions, or at least give you some hints about explaining it in...

Any luck creating an example repo?

I'm glad you've got a workaround...but unfortunately that doesn't help me know how to fix things any further. Since you mention that --no-ff works with the test repo you generated,...

Wow, nice find! Thanks so much for digging this down and sending in a PR! And I'm sorry for being so slow to respond. In any event, I really need...

> this works, I hope? That's almost what I need, but it looks like you used a username rather than a real name. Is that right? As per https://github.com/git/git/blob/4fd6c5e44459e6444c2cd93383660134c95aabd1/Documentation/SubmittingPatches#L284-L286, I...

filter-repo has multiple checks for whether something is a fresh clone. Checking for the existence of any stashes is one of them, though in your case an earlier check triggered...

fast-export and fast-import don't provide a way to iterate over the reflog (and the stash is the only place where it _might_ make sense to do so), so it's basically...

Anyway, thanks for the calm and well reasoned arguments about doing something more in a few places. I reopened the ticket on Saturday and started working on it, but still...

So, a possible idea here: * Parse the $GIT_DIR/log/refs/stash file, before filtering. * Add all refs (2nd column) to the arguments passed to fast-export * After filtering, look at the...