Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for force push
See original GitHub issueDescription
I’d like to request adding a new feature to support force pushing to a repo
Version
GitHub Desktop version: 1.0.10
OS version: Microsoft Windows [Version 10.0.15063]
Expected behavior: GH Desktop should ask me if it should do a force push or add a dedicated button for pushing & pulling, the same way SourceTree does.
Actual behavior: I get an error:
Issue Analytics
- State:
- Created 6 years ago
- Reactions:124
- Comments:30 (7 by maintainers)
Top Results From Across the Web
Force Push in Git - Everything You Need to Know | Tower Blog
In this article, we will answer all the most popular questions surrounding the powerful Force Push command.
Read more >Specify who can force push to a repository | GitHub Changelog
As shown in the image below, select Allow force pushes and Specify who can force push.
Read more >git push --force and how to deal with it - Evil Martians
What to do if you have accidentally force pushed to the wrong git branch: a step by step tutorial.
Read more >How do I properly force a Git push? - Stack Overflow
Don't forget that your remote repo permissions (read: Azure DevOps) for your account, might not grant permission to force push. In that case, ......
Read more >You Should Force Push More - Hugo Tunius
Git's force push feature is the source of a lot of controversy and errors. ... --amend > git push origin add-support-for-universe-implode -f.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@joshaber Can this be reopened. There’s clearly a lot of interest here:
For me, force pushign is a natural part of my git workflow. I’ll commonly make a commit, then amend it numerous times until it has the right shape for me. However, all throughout that i’m still pushing it as i want CI coverage to ensure good info at every step of the way.
Thanks!
👍