![]() If you make it a regular habit, you might mistakenly use it and lose your local work unintentionally.You can sync your local branch with the remote repository by pulling any commits that have been added to the branch on GitHub since the last time you synced. However, use this technique with caution. Using the above technique to force overwrite your current workspace can save you time. Warning: The above command will delete all untracked files from your workspace. Also, if you want to get rid of untracked files, you can use the following git command: You can use the above method to make sure all of your versioned files are force synced with your remote origin. Special Tip: During a continuous integration/ continuous delivery ( CI/ CD) process, the CI/CD system might not pull the latest changes if the workspace is not cleaned properly. ![]() So the git force pull has got rid of user2's local changes and reset it to origin master. ![]() Now if you check user2 history, you see that 1e2c8d3 change has been replaced by 3713dfc change (Your local hashes will be different). ![]() (If you are working with branches, use the branch name instead of master branch). The following method is the most effective way to force git pull: But user2 decides to get rid of the local changes and start from where user1 left off. Remote: Total 3 (delta 0), reused 0 (delta 0)įrom /Users/_work/LearnGIT/git_force_pull/repository/myprojectĬONFLICT (add/add): Merge conflict in Image2.txtĪutomatic merge failed fix conflicts and then commit the result.Īt this stage, if you check the history of user2's workspace, you see that user2 has the following log: Remote: Compressing objects: 100% (2/2), done. So user2 pulls changes and runs into a problem: User2 creates and commits the code locally.īut user2 decides to see if any other user has made changes. Now let's go to the user2/myproject folder. In the user1/myproject folder, the following steps take place: After a while, user1 commits and pushes the changes to remote repository. Both users start working on Image2.txt file locally. Now let’s go to the user2 folder and clone the remote repository.īoth user1 and user2 have the same Image1.txt and ReadMe.txt files. Git clone /Users/_work/LearnGIT/git_force_pull/repository/myproject.git Then, push the change to the remote repository (please use your clone path). Now let’s go into the user1 folder, clone the empty repository, and add two files ( ReadMe.txt and Image1.txt). This is going to be the remote repository. The example below starts from scratch, so you can try it out on the test repository before you use it with a real environment. If you’re trying this out in a live environment, you can end up losing your work. Warning: The below technique to force git pull will delete your local changes. Let’s create a situation where this might happen. The git pull command might not be enough to force this kind of overwrite. However, there might be cases where you want to git force pull to overwrite your local changes. In most cases, you want to resolve the conflicts manually. When multiple users are working with the same Git files and folders, you can run into conflict issues that might be tricky.
0 Comments
Leave a Reply. |