Skip to content

Drag'n'drop operation confirmations - #178

Open
eagafonov wants to merge 1 commit into
tibirna:masterfrom
eagafonov:operation-confirmation
Open

Drag'n'drop operation confirmations#178
eagafonov wants to merge 1 commit into
tibirna:masterfrom
eagafonov:operation-confirmation

Conversation

@eagafonov

Copy link
Copy Markdown

The patch adds a confirmation dialog for most destructive operations, like pushes, removing tags/branches, rebasing.

The rationale for this change is quite silly: my mouse button became flaky and started dropping commits in wrong places when I was rebasing them by drag-and-drop. I was really annoyed with that, and implemented this confirmation dialog.

Some examples:

image image image

@eagafonov

Copy link
Copy Markdown
Author

The author date of the original commit is not an error. It is really 6+ y/o. It's time to share it.

@tibirna

tibirna commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Thank you very much for this. Confirmation of destructive operations is good UX principle. While testing this, I noticed the following:

a) when dropping a patch file (from the file manager) onto qgit's window, I now get two dialogs in succession: the one you added then, immediately, the one that asks if the patch is to be applied to the workspace or as a commit. That second dialog also has a "Cancel" option, which doubles the functionality of your newly added dialog.

b) in some situations, an option (checkbox) to not ask for confirmation again would be useful for some users. I am aware that adding a persisted confirmation waiving mechanism would add quite a bit of complexity (like saving the user option to settings file and adding a global option in the settings dialog to reset the confirmation waiving).

c) the "rebase" confirmation dialog is a bit verbose and difficult to read. Trimming the displayed SHAs to 8-12 characters would help.

Thanks for your attention.

@eagafonov

eagafonov commented Jul 17, 2026

Copy link
Copy Markdown
Author

Hey,

when dropping a patch file

I've never used that :) I'll check and updated the patch for this use-case

in some situations, an option (checkbox) to not ask for confirmation again would be useful for some users

Nice idea. I'll try to implement something.

the "rebase" confirmation dialog is a bit verbose and difficult to read

Yep, though I do not notice that anymore, but just click OK. I'll make prettier version of it.

BR, Eugene.

Add a Yes/No box used by rebase, merge and moving local ref.

Add a three-way box (Push / Force push / Cancel) for push to remote
repos.
@eagafonov
eagafonov force-pushed the operation-confirmation branch from 0561f1e to b76c85c Compare July 31, 2026 05:27
@eagafonov

eagafonov commented Jul 31, 2026

Copy link
Copy Markdown
Author

Hi!

I've update the patch: fixed double dialog on dropped patch and refactored confirmation dialogs a bit.

I added a dedicated confirmation for push operations with explicit "Force push" button instead of puni check-box.

All commit's SHAs should be are truncated

@eagafonov

Copy link
Copy Markdown
Author

I havn't added "not ask for confirmation again" yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants