Using theirs option in Git merge
When developing software using Git, you can create different branches for different functions, but conflicts may exist between different branches.
This article will explain how to use the command with theirs
the -c option git merge
to resolve conflicts.
Use git merge
the command with
Gittheirs
git merge
The command can merge two or more development histories. However, sometimes this merge cannot be completed due to conflicts between branches.
ours
theirs
The files in or should be discarded to resolve this conflict.
ours
Refers to the original working branch with Git history permissions, theirs
and refers to the branch that contains the new application commits.
You can use git merge -s ours
discard ours
changes in . This command discards all changes from other branches and leaves the files on your branch unchanged.
When you next merge from another branch, Git will only consider the changes made from that point on. However, -s
the -d option cannot theirs
be used with .
--strategy-option
Resolving conflicts in Git
using
Alternatively, we can use theirs
with the -X
or --strategy-option
options.
-X
-s
The main difference between the -m and -m options is that -X
-m performs a regular recursive merge, resolving any conflicts using the chosen side, whereas -s
-m changes the merge to ignore the other side completely.
The following commands use theirs
to resolve any conflicts.
git merge -X theirs branchname
Merging using temporary branches in Git
Use the command below to test2
merge into the checked out test1
.
Switch to test1
the branch.
git checkout test1
Merge commits without conflicts. ours
The contents of will be discarded later.
git merge -s ours test2
Create a temporary branch.
git branch temp
Use git reset
the command to set it HEAD
. It test2
gets the content from the branch.
git reset --hard test2
Reset to a merge commit but git reset --soft
keep the contents using the command.
git reset --soft temp
Change the contents of test2
the merge commit with the contents of .
git commit --amend
Delete the temporary branch we created earlier.
git branch -D temp
You can see that the merged commit contains only test2
the contents of .
git diff HEAD test2
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git diff shows diff details of uncommitted changes
Publish Date:2025/03/31 Views:105 Category:Git
-
This article outlines how we can get diff details of uncommitted work in Git. We use the git diff command to show the differences between various Git references, such as commits, the index, and the working tree. We can use this command to d
Staging area in Git
Publish Date:2025/03/31 Views:151 Category:Git
-
In this article, we will learn about the staging area in Git . Git is a version control system that maintains a history of changes made to a project directory. Git uses commits to track changes. Git has three internal management systems, on
Add all files in a folder to commit in Git
Publish Date:2025/03/31 Views:158 Category:Git
-
This article will discuss the necessary steps to add all of your files into one folder for submission. If you have a folder with a dozen files, adding the files one by one can be tedious. Fortunately, Git allows us to add all the contents o
Meaning of Fetch_Head in Git
Publish Date:2025/03/31 Views:64 Category:Git
-
This article defines Fetch_HEAD in Git . This reference is an integral part of the git pull command and is important when merging changes from a remote repository into a local repository or branch. If you're not sure what Fetch_Head means,
Get all branches in Git
Publish Date:2025/03/31 Views:62 Category:Git
-
This article discusses how to fetch all branches from a remote repository. The git fetch command is a useful utility when you want to download changes from a remote repository without having to update your local branches. Sometimes, you may
Clone a Git repository with a specific revision
Publish Date:2025/03/31 Views:82 Category:Git
-
This article discussed various methods that we can use to clone a Git repository with a specific revision or changeset. This comes in handy when you have a repository with large files and you only need a specific version of the code. Instea
Squash commits pushed in Git
Publish Date:2025/03/31 Views:86 Category:Git
-
This article outlines the process of squashing commits that we have pushed to a remote repository. We squash the commits into one to reduce clutter in the repository. To squash the commits, we run git rebase in interactive mode . Squash com
Git squash all commits
Publish Date:2025/03/31 Views:65 Category:Git
-
In every developer’s life, the word squash is often used while working with the Git distributed control system . This feature in Git is a handy option that developers often use to achieve a neat workflow in their development team. In this
Close the Git commit editor on Windows
Publish Date:2025/03/31 Views:62 Category:Git
-
In this article, we will discuss how to exit the Git commit editor. This can be a little tricky, especially if you are new to Git bash . Let's see how to exit the editor on Windows. Close the Git commit editor on Windows We will look at a t