I've recently updated to SourceTree version 2.4.8 and a change has been made to the behaviour / options when changing branch which disrupts my workflow.
In previous versions when changing branch the pop-up would give you a tickbox option to "Discard local changes", however since version 2.4.8 this option has changed to "Stash local changes".
I would like to have the previous "Discard" option back - am I able to change this in any way?
I'm running SourceTree on macOS Sonoma 14.3.
Thanks.
I agree, this change now requires me to discard changes manually before switching branches.
Bump / +1. "Stash" instead of "discard" is awful.
Please let users select the behavior with a check box in preferences!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is it possible to "downgrade" ?
upd:
anybody that stuck with it can download version 4.2.7
from here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I now have tons of useless stashes. Please allow us to discard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 to get back "Discard local changes"!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Incredibly annoying! Please bring back the option to discard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, I would much prefer discard vs stash when switching branches
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, same for me, this is annoying
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.