-
-
Notifications
You must be signed in to change notification settings - Fork 605
support force push #274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For this, would it not be better to create a separate command/key for it? Usually when you want to force push, you know, it's not like you usually push, fail and decide to force push, this would probably result in overwritten commits and annoy everyone else who was contributing who would then have to So I think this should be on a separate key, perhaps Shift-P? |
Hello. |
@WizardOhio24 ok lets do |
I know this is an old issue but this message seems like the intent is to have a confirmation popup for when you are force pushing. I would like that so I do not accidentally force push. did the confirmation get removed? is there a way I can change some configuration to require a confirmation before force pushing? Thanks! |
Nevermind! it appears the confirmation works as expected! The problem was I tried re-mapping shift+p to ctrl+p for force push with the following:
But I didn't realize that when you use control modifier, you have to make sure the character
|
Does it actually do a push with |
@cloudlena its good ol --force |
see libgit2/libgit2#4286 for how to do
force
with libgit2we should try to push first and if it fails we ask if we should force push, this way we only need one
push
commandThe text was updated successfully, but these errors were encountered: