First, make sure that you can push manually without providing your password. If you are pushing over HTTP or HTTPS, that will be a case of either creating a .netrc file with the login details or adding your username and password into the URL for the remote. If you’re using SSH, you can either create … Read more
force overwrites a remote branch with your local branch. –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. I … Read more
Git generally doesn’t throw anything away, but recovering from this may still be tricky. If you have the correct source then you could just push it into the remote with the –force option. Git won’t have deleted any branches unless you told it to. If you have actually lost commits then take a look at … Read more
Best Option Probably the cleanest, least confusing, and safest way to push into your non-bare remote repository, is to push to dedicated branches in the remote that represent your laptop branches. Let’s look at the simplest case, and assume you have just one branch in each repo: master. When you push to the remote repo … Read more
You need to make sure that no other users of this repository are fetching the incorrect changes or trying to build on top of the commits that you want removed because you are about to rewind history. Then you need to ‘force’ push the old reference. git push -f origin last_known_good_commit:branch_name or in your case … Read more
Just do: git push origin <your_branch_name> –force or if you have a specific repo: git push https://git…. –force This will delete your previous commit(s) and push your current one. It may not be proper, but if anyone stumbles upon this page, thought they might want a simple solution… Short flag Also note that -f is … Read more
You should be able to force your local revision to the remote repo by using git push -f <remote> <branch> (e.g. git push -f origin master). Leaving off <remote> and <branch> will force push all local branches that have set –set-upstream. Just be warned, if other people are sharing this repository their revision history will … Read more
You can control the default behavior by setting push.default in your git config. From the git-config(1) documentation: push.default Defines the action git push should take if no refspec is given on the command line, no refspec is configured in the remote, and no refspec is implied by any of the options given on the command … Read more
A common cause is cloning using the default (HTTPS) instead of SSH. You can correct this by going to your repository, clicking “Clone or download”, then clicking the “Use SSH” button above the URL field and updating the URL of your origin remote like this: git remote set-url origin [email protected]:username/repo.git You can check if you … Read more
Git push error ‘[remote rejected] master -> master (branch is currently checked out)’