I updated to 3.0.12 this morning, and ever since I can no longer do a force push, which I often use in combination with Amend latest commit. The option is enabled in Options, Git. And I also checked/unchecked 'Use Safe Force Push'.
When the checkbox for Force Push is checked, and I click 'Ok' in the Push window, the window closes but nothing happens.
The workaround I found is to manually enter the git command: when I manually do "git push --force etc" the push is executed. There is no error.
I was seeing the same issue. Here is a workaround inside SourceTree itself instead of via the command line:
Open the SourceTree Options, go to the Git tab and uncheck the "Check submodules before commit & push" option.
You should probably not use this workaround if your submodules are under active/frequent development, but if they're relatively stable, then it should be safe.
I don't know the underlying reason this is happening, but at least this should allow you to force push again.
No, there is nothing indicating an error in the console. I have checked 'Always display full console output' now. After clicking on the button 'Push' the Submodule check window is shown very briefly. It's almost as if it finds there is nothing to push. My local branch is checked by the way.
Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...