Let’s start by understanding what’s happening in the background… 2. Joe won’t be happy when he’s back from the gym!ĭoes this mean that we should avoid Force Pushing at all costs? Not necessarily. In the scenario above, if you force push your work, you will erase Joe’s commit from the remote repo. This can look like an easy workaround when the git push command does not work, but it is rarely recommended - it’s not the default behavior for a reason. You can use the -force flag (or -f for short). If you have a look at Git’s official documentation, you will quickly notice that you can force this command. And since Joe committed his work in the meantime, the repo’s history changed and you aren’t up to date anymore. You won’t be overwriting commits from the team by accident but, at the same time, this means you will always need to pull any outstanding changes before pushing your work. This is a good thing because it reassures you that the repo is in a healthy state at all times. Unlike other version control systems, Git does not allow any conflicts on the remote repository.

Hint: See the 'Note about fast-forwards' in 'git push -help' for details. You may want to first integrate the remote changes This is usually caused by another repository pushing Hint: Updates were rejected because the remote contains work that you do Sadly, an error message is displayed in your terminal window, similar to this: ! main -> main (fetch first) You conclude your work, and now just need to run git push to end your day. Joe is on his way to the gym and you carry on with your assignment. Joe has finished his task and pushed his work to the remote repo. You both pulled the latest version from the remote repository in the morning and started working.

Here’s a simple scenario: you are working on the same branch as Joe. If not, don’t worry - after reading this article, you will.

Github desktop force push