Updated description:
It would be great if Fork supported an option to auto-force-push-with-lease, in certain situations where you know you're going to rewrite history by doing something locally, and where it should be safe to force-push given the lease checks.
Primary cases for this, for me, are rebasing and amended commits.
After these situations I get the classic 1-in-1-out
and I have to then manually force-push an extra step.
I have "Automatically push on commit" enabled, and so if I don't do the force-push quickly enough, I get an error when the auto-push fails.
I would love it if I could tick a box somewhere that told Fork to detect this situation and automatically do the force push for me.
This should obviously be opt-in. It could be a global setting, or a tick-box in the UI of the action that was going to cause the rewrite (or both).
Original description:
Directly Support --force-with-lease
Git has a git push --force-with-lease mode which is a safer way of force-pushing, as it checks the destination first to make sure that it is pointing at the expected commit.
It would be great if Fork supported this directly, and offered to push in situations where you know you're going to create a divergence between the local and remote
…
Updated description:
It would be great if Fork supported an option to auto-force-push-with-lease, in certain situations where you know you're going to rewrite history by doing something locally, and where it should be safe to force-push given the lease checks.
Primary cases for this, for me, are rebasing and amended commits.
After these situations I get the classic 1-in-1-out
and I have to then manually force-push an extra step.
I have "Automatically push on commit" enabled, and so if I don't do the force-push quickly enough, I get an error when the auto-push fails.
I would love it if I could tick a box somewhere that told Fork to detect this situation and automatically do the force push for me.
This should obviously be opt-in. It could be a global setting, or a tick-box in the UI of the action that was going to cause the rewrite (or both).
Original description:
Directly Support --force-with-lease
Git has a
git push --force-with-leasemode which is a safer way of force-pushing, as it checks the destination first to make sure that it is pointing at the expected commit.It would be great if Fork supported this directly, and offered to push in situations where you know you're going to create a divergence between the local and remote
…