Waleed Khan

Hi @azaslavsky, thanks for reporting. I think this is a limitation in the `git2` crate, and arguably in libgit2 itself. In libgit2, it claims that an empty email is invalid:...

You may also need to pass `--reset-author` or similar to fully reset the signature. Make sure both the author and committer signatures have been updated.

Hi @mlanln, sorry to hear that this is happening. Another user also [reported this on Discord](https://discord.com/channels/915309546984050709/1090626066697166899), but unfortunately we were unable to find a solution; they ended up recloning the...

@mlanln can you try with a version of Git earlier than 2.40? Maybe something about the index format changed and libgit2 hasn't upgraded to handle it yet.

@mlanln Thanks for confirming. I'll leave the issue open in case others run into the same problem. I also very recently updated our version of `git2` (in https://github.com/arxanas/git-branchless/commit/f25babf6dbc4979003acf24c7ebf78e89a01f157); if you...

It looks like it's this issue in libgit2: https://github.com/libgit2/libgit2/issues/6531 You can follow [the workaround here](https://github.com/tummychow/git-absorb/issues/81): > workaround is to disable the offending option git config --local index.skipHash false. then you...

Hi @mlcui-google, thanks for reporting. I'm not sure how difficult these issues will be to fix; if you want a more reliable solution to rewording/rewriting merge commits, you can also...

Hi @melko, thanks for reporting! Unfortunately, I am running on macOS, and it seems like it would be quite a hassle to get an NFS filesystem running to reproduce this....

The smartlog doesn't indicate the current rebase status (but maybe it should). Generally speaking, if you're stuck in a rebase, then you should use `git rebase --abort`; it shouldn't be...

This behavior makes sense for rebases (in the case that a change was applied upstream), but not for rewords. It looks like it happens here for the in-memory code path:...