JIYIK CN >

This article will discuss the difference between the git push --force-with-leaseand commands. Usually, we use the command to publish local changes to the remote repository.git push --forcegit push

Let's go ahead and examine these commands.

git push --forceOrder

To publish local changes to the remote repository, we run:

$ git push origin

However, in situations where multiple developers share our remote repository and publish their changes to the remote repository, Git can refuse to push.

To force Git to publish our commits, we git pushadd --forcethe -p flag to our -p command, as shown below.

$ git push --force origin

The disadvantage of using this command is that it does not take into account changes pushed to the remote repository by other developers. This command will overwrite the repository based on the state of your local repository.

This can be dangerous as it can disrupt our project timeline. If you want to push your changes to the remote repository and keep the changes made by other developers, you can do so.

git push --force-with-leaseOrder

This command comes in handy when multiple developers share a remote repository. We use it when publishing changes to avoid discarding changes pushed by other developers.

$ git push --force-with-lease origin

Let's look at an example. This is the current state of our remote repository.

We will README.mdmake some changes to the files and commit the changes on GitHub. Note the commit ID outlined 097ab8b.

This is what it looks like now.

Note the commit ID ba29c53.

We will now open the file on our computer README.md, make some more edits, commit the changes, and then try it out git push.

Git rejected our push attempt because the commit histories are different. We could run git push --forcethe command, but this would discard the changes we made in GitHub.

We can execute git push --force-with-leaseas shown below.

$ git push --force-with-lease
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 314 bytes | 314.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To https://github.com/Wachira11ke/Delftscopetech.git
 + b7b8e6a...8ddd086 main -> main (forced update)

git push --force-with-leaseThe difference between and git push --forceis the result. leasePushing changes with helps us avoid discarding changes pushed by other developers.