Sourcetree Windows 3.0.12 no longer force push

[kxk4xyh]

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.

[Andrew Kessel]

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.

[minnsey]

Hi

Is there anything indicating an error in the console? You can make sure the console stays open by checking the 'Always display full console output' option in the Tools/Options/General tab

[kxk4xyh]

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.

[David Worsley]

I have been experiencing exactly the same thing since upgrading to 3.0.12.  I would appreciate any suggestions.

[minnsey]

Does the repository have submodules? If so are your changes in the parent or submodule?

[David Worsley]

In our case, yes, the repo has one sub-module.  The failed force pushes have been to the parent, however.

[Sylvain Duchesne]

Same issue here, and it seems to only be when projects have submodules

[minnsey]

Thanks for the information I've raised the following ticket, please add any additional details there.

[stefan-unimaze]

Any update on this problem?

[Preben Fihl]

Link to the issue (if someone else is looking for this):

https://jira.atlassian.com/browse/SRCTREEWIN-11297

[Shawn Fox]

It is still a problem using source tree 3.4.17. Using the force push option as a work around does still work for me.  The application provides no feedback as to what the problem is.  Is simply doesn't respond to the request after pushing the button to push changes.

[Florin ION]

Same issue here, regarding force-push, using source tree 3.4.17 :(
Is there a workaround?