Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,795
Community Members
 
Community Events
168
Community Groups

Sourcetree Windows 3.0.12 no longer force push

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.

2 answers

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.

0 votes
minnsey Atlassian Team Dec 10, 2018

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

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.

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

minnsey Atlassian Team Jan 09, 2019

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

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

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

minnsey Atlassian Team Jan 25, 2019

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

Any update on this problem?

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

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Bug Fix: Sourcetree for Windows authentication error when updating to app password

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...

78,652 views 134 29
Read article

Atlassian Community Events