ok, yess... Be able to switch to the other list feels nice.. 👌

from some adhoc testing, I found a edge case.

1. Make some changes to a file and save.
2. go to unstage changes and open the Unstage Changes view of the file
3. Discard all the changes you made by selecting all the hunks and clicking discard selection.
4. File disappears from Unstaged Changes (expected)
5. Make a change to the same file and save
6. Open the file.

Expected: Shouldn't have the ability to Undo Last Discards since all changes were already discarded and it's a new edit.

Actual: Unstage Changes has Undo Last Discards, but when you click on it, it says the file has been edited.

@ungb thanks for testing and bringing up this edge case! This one's tricky because in theory we can actually allow people to undo their last discard even if the file has been changed since the discard.

One thing to keep in mind is that the text buffer's undo history and the undo last discard history for the file diff are completely separate mechanisms and thus one can theoretically make changes to a buffer and still be able to undo discards.

We can in theory undo a discard even after the file has been modified by applying a patch that has the discarded lines to working directory version of the file. If the discarded lines are in a different part of the file than the new modifications then the patch should apply cleanly without conflicts.

I say "in theory" because we haven't yet implemented a version of this feature that allows users to undo their last discard if the file has been modified since the discard. This was for the sake of shipping something quick and simple up front, but there's certainly room for us to iterate and make the undo last discard feature even more flexible.