You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When I click the "Push" button in the SourceTree window I get a window asking me to select the desired branch and at the bottom of this window there is an option to "Force Push" (which is necessary after a rebase). Unfortunately, this option is grayed-out and I am not able to select it. Why is this option not selectable?
I'm using Sourcetree 220.127.116.11 on Windows 10
That's surprising because I have been rebasing and force pushing in 2017. It's only in the last few weeks (maybe few months, I can't remember exactly when I noticed this issue) that the option became grayed out and prevented me from force pushing.
Anyway... it's working now so I'm happy.
One more comment: in order for me to force push I have to check the "Force Push" checkbox in the "Push" window, and then I get another window telling me that "one or more branch is selected to force push. This may result in a destructive operation" and asking me to confirm that I really want to force push. Is a "Enable Force Push" global setting really necessary? I understand force pushing is potentially dangerous but I must already take two actions to demonstrate that I really want to perform this action. Is a third failsafe really necessary?
If Atlassian feels that this global setting is necessary, I suggest a tooltip that would show up when I hover my mouse over the grayed out "Force Push" and would say something like: "in order to enable this option you must enable the global option and thus demonstrate that you understand the potentially dangerous nature of force pushing".