Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,556,699
Community Members
 
Community Events
184
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
Atlassian Team members are employees working across the company in a wide variety of roles.
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
Atlassian Team members are employees working across the company in a wide variety of roles.
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
Atlassian Team members are employees working across the company in a wide variety of roles.
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
AUG Leaders

Atlassian Community Events