Files appearing in unstaged area post rebasing

[saphal1998]

After a rebase, the files seem to be modified but not committed, i.e. they appear in the staging area. Ideally we would want an empty staging area at the end of the rebase.

@taneliang feel free to add more context here

[taneliang]

Thanks! I stumbled upon nodegit/nodegit#1217 that seems pretty much identical to what we're seeing. Seems like this may be a bug on their side? There's also a workaround there that I didn't really understand but maaay be worth trying.

Anyway, more detailed repro notes:

1. Clone https://github.com/24r/stack-attack-issue-65-repro/commits/main
2. Rebase commit named "6" onto "4"

The rebase will succeed, and the resulting commit history matches what we expect. However, git status will show that commit 5's changes are present and staged but not committed.