I've upgraded my SourceTree and now my Finish Release has changed the way it interacts with Bitbucket.
Using the Git-Flow button I would Start a Release, then I would create a pull request in bitbucket to for merging the develop branch into master.
Then I would Finish Release in SourceTree I would select Tag with message, Delete branch and Push changes to remote.
The pull request in bitbucket would show Merged remotely after sourcetree was done.
Now after I upgraded it declines the pull request instead of showing it as merged remotely.
Is there anyway to get it to go back to merged remotely?
Bitbucket was not changed, just SourceTree was upgraded.
Thanks in advance
Thank-you for your response!!
Correct, actions are the same.
Atlassian Bitbucket v5.3.1, SourceTree 3.0.9 (although I was going to update to the latest 3.0.12 pretty soon)
I was thinking it might be a new setting in SourceTree that it passes to GIT, or a change to a default setting and we just need to change it in our config to get it to go back to the way it was. But I haven't found any mention of this situation any where.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event