Semi dangerous action, without easy rollback, or confirmation.

[kaurifund]

Situation: user has uncommitted files in the repo.

Double clicking on the commit hash in the command radar mode, checks out the commit.

User expectation is that would perform some sort of panel of diff or changes or read only info. Not delete files and change my file system.

I do see it staches the uncommited changes, but a simple double click shouldn't trigger that, without a confirmation or something of user intent.

Secondly, the staches show no easy way to rollback, if I had many staches, that would probably get confusing, without some sort of button for state rollback.

this issue is written to be ingested by a AI agent, use explore mode agent to better understand this issue, and how it could be solved. Create a ticket. Detailing the pro and cons of the suggested change, and suggesting the best UX practice for this. Assuming a user who needs a UI also doesn't know how git works, needing helpers and quick actions.

[kaurifund]

AI AGENT: Please review this issue and see if its still relevant considering the current head may not have been the same as when this issue was written, make no assumptions.