We have a release branch where all feature branches are merged, and for bug fixes, we create new branches from the release, fix the issue, and raise a PR to merge back. I created a new Dev branch from the release, made my changes, and raised a PR to the release branch, which showed a merge conflict. During conflict resolution, only two files had differences: one from my changes and another from someone else’s. I resolved the conflict, and since the PR was already approved, I merged it without noticing any differences in the diff. A new commit was created for the merge conflict, and everything seemed fine at the time. However, after my merge, several changes were made to the release branch by other developers. By resolving the conflict in my Dev branch, I unintentionally aligned the pointers of the release and dev branches, causing changes made after the creation of my dev branch to be lost. Now I can see the unintended impact of my conflict resolution, and some changes are missing from the release branch.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Getting Error while merging code from my dev branch to my non-prod branch | 0 | 317 | February 17, 2022 | |
I got a merge conflict while merging code from my dev to my nonprod | 0 | 213 | February 18, 2022 | |
Merge request also modifies source branch | 5 | 5370 | May 16, 2023 | |
Merge Conflicts in MR with dev and main branch | 3 | 1774 | February 16, 2024 | |
Cherry-picking MR with already resolved conflicts does not work | 0 | 205 | November 16, 2023 |