Remove 'undo commit' command from gitlens inspect

[d13]

Discussed in #2745

^{Originally posted by mdj-uk June 16, 2023}
When in the gitlens inspect file history, or commit history, there is a button to undo the latest commit (the first icon from the left):

I find it very easy to hit that accidentally, which makes me scared to use just about any gitlens feature.

Is there any way to remove it, or to require a confirmation step? I couldn't find any option in the extension settings.

[yurymann]

Is it possible to bump the priority of this, please?
As a new GitLens user, I discovered this "feature" accidentally yesterday and was upleasantly surprised. Have to pay explicit attention now to not hitting it every time I navigate in that panel.

Any action affecting working copy should ask for a confirmation.

[eamodio]

Fixed by 056e19c (wrong commit message)

Moved Undo Commit to Commit submenu

[eamodio]

Can you please verify this fix in tomorrow's (v2023.12.05xx) pre-release edition of GitLens? Thank you so much!

You can switch to the pre-release edition of GitLens, by clicking on the "Switch to Pre-Release version of this extension" from the Extensions view.

[yurymann]

@eamodio I've just tried v2023.12.504 and didn't notice any change: the same Undo Commit button is avilable and when pressed, updates the working copy. What was supposed to change?

Sorry, can't attach the screenshot as I was testing it on the work machine.

[eamodio]

@yurymann Are you looking at this in the File History or Line History views?

[yurymann]

In Commits on the Source Control panel. Please see the picture.
Sorry if it was not clear before - I assumed that it uses the same widget in all the views.

[mdj-uk]

For me it's removed from the file history:

but still present in the commit history:

That's after selecting the pre-release version of the extension v2023.12.704.

Is the plan to remove it from the commit widget as well?

[eamodio]

No, this is only for the File History & Line History. You can open another issue for the Commits view, but given the usage and intent in that view I'm not convinced on removing that option, but if there is enough community agreement we can revisit.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.