How to resolve conflicts on applying stash in SourceTree?
Asked by bpiec:

There can be conflicts when applying stash changes. Currently SourceTree just displays an error message and the conflicting files contain changes from both versions. Cannot it just apply the same mechanism as in merge conflicts?


Answers:
author: barathwaja
body: Is there any implementation undergoing from **SourceTree Team side [@Mike Corsaro](/t5/user/viewprofilepage/user-id/842547)** for solving this merge conflicts from *SourceTree* itself? Similar to what GitHub Released today.

FYI, <https://blog.github.com/2018-11-14-github-desktop-1-5/>


author: Mike Corsaro
body: Hello! When applying a stash that causes merge conflicts, you'll need to resolve the conflicts yourself. The file list should look the same as when you have a normal merge conflict.

comments: author: bpiec
body: That doesn't help me. I know that I need to merge conflicts. I am just asking if SourceTree wouldn't be able to help me by providing the same mechanism as when merging.


author: Mike Corsaro
body: I'm not sure what you mean. Are you requesting that ST have a new feature that allows for merging conflicts in-app?


author: bpiec
body: When I do a merge it presents me a list of conflicting files and allows me to resolve them one by one (using external merge tool). When applying a stash there is no such thing.


author: Adrian Cigher
body: I thouht I have the same issue, but then I switched back to Source Tree and the local changes were there ready to be solved and commited. Maybe it just didn't refresh the UI. Only after minimizing/switching back to Source Tree.


author: alex75
body: I had the same problem: after the message there is no files listed.  
I tried to minimize and resize the window, not solved.  
I switched repository and return to this one and magically the file list appeared, with the the conflicted files.

Windows 10.   
SourceTree v 2.3.1.0 (windows app version)


author: Kevin Brammer
body: The file status view is bugged since a few versions not refreshing and or freezing completely. I made a few bug reports on this (same as the windows size and drag an drop-ability not working) but no one seems to care.

An easy work around for your problem is to apply the stash, go to the file status tab and press F5. This will refresh the view and your conflicts will show up as usual.

Hope this Helps,

Kevin


author: Peter Hitchmough
body: Thanks for the F5 tip [@Kevin Brammer](/t5/user/viewprofilepage/user-id/369497).


author: Oscar Persson
body: The F5 tip worked for me. Thanks [@Kevin Brammer](https://community.atlassian.com/t5/user/viewprofilepage/user-id/369497)


author: lloydlcs
body: Works for me too. Thanks [@Kevin Brammer](/t5/user/viewprofilepage/user-id/369497) :)


author: arslanfurkanfatih
body: Thanks . It works [@Kevin Brammer](https://community.atlassian.com/t5/user/viewprofilepage/user-id/369497)


author: J?nas Sigur?sson
body: Had the exact same issue as described above. Solved by refreshing. Interesting that this hasn't been fixed for so long. Thanks for the help guys!


author: Scott Wilkinson
body: Still an issue. Is there an open issue we can vote for?


author: Andrew Whitegiver
body: Still an issue. Refresh solved it.


author: Brett May
body: 2021 and this is still an issue


Tags: git