You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have the option to choose force push with lease in the drop down menu of the Git Staging view:
Motivation
From SA:
--force-with-lease is a safer option that will not overwrite any work on the remote branch if more commits were added to the remote branch (by another team-member or coworker or what have you). It ensures you do not overwrite someone elses work by force pushing.
Since the chosen option isn't always visible I often end up having force push on without thinking about it and force push with lease would stop me from overwriting changes from my collaborators.
Alternatives considered
Make it always visible that the force push option is turned on, might be a viable option as well. If it's feasible in the UI that might be a worthwhile change anyways.
Additional context
No response
The text was updated successfully, but these errors were encountered:
fapdash
changed the title
Allow force push with lease (--force-push-with-lease)
Allow force push with lease (--force-with-lease)
May 16, 2024
fapdash
changed the title
Allow force push with lease (--force-with-lease)
Allow force push with lease option in the Git Staging view (--force-with-lease)
May 16, 2024
Description
I'd like to have the option to choose force push with lease in the drop down menu of the Git Staging view:
Motivation
From SA:
https://stackoverflow.com/a/52823955
Since the chosen option isn't always visible I often end up having force push on without thinking about it and force push with lease would stop me from overwriting changes from my collaborators.
Alternatives considered
Make it always visible that the force push option is turned on, might be a viable option as well. If it's feasible in the UI that might be a worthwhile change anyways.
Additional context
No response
The text was updated successfully, but these errors were encountered: