Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
On branch-x, I do git merge branch-y Now there are some conflicts, and git status shows Changes to be committed: new file: a new file: b Unmerged paths: (use "git a...
#3: Post edited
by
Quasímodo
·
2022-08-06T16:10:57Z (over 2 years ago)
Fix unadequate syntax highlighting
- On branch-x, I do
git merge branch-y- Now there are some conflicts, and `git status` shows
```- Changes to be committed:
- new file: a
- new file: b
- Unmerged paths:
- (use "git add <file>..." to mark resolution)
- both added: w
- both modified: x
- both added: y
- both modified: z1
- both modified: z2
- ```
- Specifically, the conflict of files `z1` and `z2` I have to resolve manually (by inspecting and eliminating the `<<<<<<< HEAD`, `>>>>>>> branch-y` markers).
- But for all other conflicts, I want to keep the local changes, as if I always chose the `<<<<<<< HEAD` segment and never the `>>>>>>> branch-y` one.
- I could of course do that manually, but there are many files left.
- **How can I merge all the remaining files by keeping the local branch changes only?**
- I found `git merge --strategy-option ours` but that doesn't seem to work for an already started merge:
```- error: Merging is not possible because you have unmerged files.
- hint: Fix them up in the work tree, and then use 'git add/rm <file>'
- hint: as appropriate to mark resolution and make a commit.
- fatal: Exiting because of an unresolved conflict.
- ```
- On branch-x, I do
- ```none
- git merge branch-y
- ```
- Now there are some conflicts, and `git status` shows
- ```none
- Changes to be committed:
- new file: a
- new file: b
- Unmerged paths:
- (use "git add <file>..." to mark resolution)
- both added: w
- both modified: x
- both added: y
- both modified: z1
- both modified: z2
- ```
- Specifically, the conflict of files `z1` and `z2` I have to resolve manually (by inspecting and eliminating the `<<<<<<< HEAD`, `>>>>>>> branch-y` markers).
- But for all other conflicts, I want to keep the local changes, as if I always chose the `<<<<<<< HEAD` segment and never the `>>>>>>> branch-y` one.
- I could of course do that manually, but there are many files left.
- **How can I merge all the remaining files by keeping the local branch changes only?**
- I found `git merge --strategy-option ours` but that doesn't seem to work for an already started merge:
- ```none
- error: Merging is not possible because you have unmerged files.
- hint: Fix them up in the work tree, and then use 'git add/rm <file>'
- hint: as appropriate to mark resolution and make a commit.
- fatal: Exiting because of an unresolved conflict.
- ```
#2: Post edited
by
Alexei
·
2022-08-05T06:04:59Z (over 2 years ago)
added relevant tags
#1: Initial revision
by
Quasímodo
·
2022-08-04T13:34:31Z (over 2 years ago)
Keep local branch changes to resolve all remaining conflicts in a merge
On branch-x, I do
git merge branch-y
Now there are some conflicts, and `git status` shows
```
Changes to be committed:
new file: a
new file: b
Unmerged paths:
(use "git add <file>..." to mark resolution)
both added: w
both modified: x
both added: y
both modified: z1
both modified: z2
```
Specifically, the conflict of files `z1` and `z2` I have to resolve manually (by inspecting and eliminating the `<<<<<<< HEAD`, `>>>>>>> branch-y` markers).
But for all other conflicts, I want to keep the local changes, as if I always chose the `<<<<<<< HEAD` segment and never the `>>>>>>> branch-y` one.
I could of course do that manually, but there are many files left.
**How can I merge all the remaining files by keeping the local branch changes only?**
I found `git merge --strategy-option ours` but that doesn't seem to work for an already started merge:
```
error: Merging is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
```