-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Undo commit" dialog: can't false warnings be transparently handled? #18388
Comments
This comment has been minimized.
This comment has been minimized.
@aybe thanks for the issue. Just to confirm -- were there uncommitted changes present in your repository, but they weren't for the The modal shows if there are any uncommitted changes (you can see some context around this in #12341 (review)). We tend to prefer to warn when at all possible since there are quite a few scenarios at play here that can cause lost data or confusion, and is also why we provide the option to disable the dialog. |
Exactly, other changes but not for the file being undo-ed. Ironically, I just realized that there is already the option to disable the behavior... I checked it and tried, yes, it is dangerous; I modified But if somehow there could be a 'smart' behavior that is between the actual ones, that would be much appreciated! |
Drive by comment. Restoring a stash does what I think is requested here and only warns if there are files with the same name in the stash and in the changes list so possibility to reuse logic. |
The feature request
Example:
.editorconfig
The actual message:
The reality:
No changes will ever be lost, file was committed in whole, there are no remaining changes that would be overwritten if undo-ing.
Proposed solution
Maybe the software could avoid showing these false warnings for such cases?
There could be an option to set this behavior.
If these messages are tied to accessibility, above option should be original behavior so as to not break accessibility experience.
Additional context
No response
The text was updated successfully, but these errors were encountered: