Gitextensions: Make "Prune remote branches" option on Pull dialog "sticky".

Bad idea. I wouldn't want this. It's a destructive action. It should be
opted in.

On Tue, Aug 8, 2017, 7:39 PM yusirui notifications@github.com wrote:

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
An option was added to the 2.50.01 Pull dialog to "Prune remote branches".
If set to "checked", it is reset to unchecked after the pull or fetch.

If the current behavior is a bug, please provide the steps to reproduce
and if possible a minimal demo of the problem.

What is the expected behavior?
Please make it a persistent setting, like the Merge options, or add a
sub-option to make it persistent.

Environment you encounter the issue:

• GitExtensions version:
• GIT version:
• OS version:

Did this work in previous version of GitExtensions (which)?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gitextensions/gitextensions/issues/3891, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADdhsd4kvzGmZEQwbefABC0zu3hb0JPfks5sWPGZgaJpZM4OxbHh
.

Maybe then add an option to make "Prune" sticky in the "Settings->Advanced" dialog?

Yes please, add this feature. Like @moshesafran said, add an advanced option to allow the user to make it "sticky".

As @vbjay said enabling this feature may have serious consequences.
When a user types a git command they are (significantly more) explicit about requested operations. However when those commands are abstracted by a UI away from the user, these command become part of the "black box".

Imagine the settings gets set, the user is/becomes unaware or forgets about it, and then loses his/her work.
That is not the risk we are willing to accept.

If you indeed need this feature, write a custom script (Settings > Scripts) and hook it up to AfterPull event (or AfterFetch once #4909 gets implemented) and run the prune command.