Community
Participate
Working Groups
It should (be able to) show changes since the parent of HEAD (HEAD^). An example is when I included a change that I did not want, so I'd like to use amend to remove it.
*** Bug 459152 has been marked as a duplicate of this bug. ***
Summarized feature requests from bug 459152: In the Git Staging view, when editing an existing commit, it should be possible to re-edit all details of a commit. This includes not only the commit message, but also all file additions, modifications and deletions. Therefore, the Staged Changes file list should list the changes that happen in the commit that is being edited. (Currently it is empty.) The menu item “Modify > Edit” should not switch to the Git Interactive Rebase view but instead to the Git Staging view, since that is the natural view to change details for a single commit. The fact that interactive rebase is used to implement this command should not dominate the UI.
Which menu item "Modify > Edit"? I guess you mean when starting from "History View" and select there "Modify > Edit" there, or? If that is the case and if I select a commit in History view which is not HEAD then I find it ok to popup the rebase view. It should be clear that modifying a single commit which is not HEAD requires that all the successor commits of that commit also have to be changed. I agree that if you select HEAD in History view and say "Modify > Edit" then we should come up with staging view.
(In reply to Christian Halstrick from comment #3) > Which menu item "Modify > Edit"? I guess you mean when starting from > "History View" and select there "Modify > Edit" there, or? Yes, I meant this. > If that is the case and if I select a commit in History view which is not > HEAD then I find it ok to popup the rebase view. It should be clear that > modifying a single commit which is not HEAD requires that all the successor > commits of that commit also have to be changed. Yes, that would indeed be good.
