Currently, I have a stable master branch and a branch with big changes on certain classes.
When using the "changes" branch, I found an error that I also want to fix on the main branch.
I fixed this by changing only one line of code on the main server.
Now I want this patch to also be added to the "changes" branch.
After reading a few answers , it was suggested that the best option would be Rebase.
When applying git rebase master
in the "changes" branch, git seems to be considering one of the conflicting files - a completely different file than before. Using mergetools --tool diffuse
, I get the following diagnostics:
![](https://fooobar.com//img/77f70f855c7f77f037dc4d2a846076ad.png)
As you can see, there is one change in the first file, tons of changes in the second and, apparently, do not overlap with anything.
My question is: is there a way to merge a small change into a heavily modified branch without spending a lot of effort on resolving conflicts? If not, what is the best way to deal with this situation?
source share