Using the tool git flow, I created a function branch (forked dev), made a bunch of changes, and merged the branch onto dev.
There is a file that I changed in the function branches. I can confirm that the revision (let it be called REV-A) that modifies the file ( FILE-A) is present and applied to the function branches.
However, after the merge FILE-Ais in the initial state (pre-merge) on the branch dev. I see REV-Awhen I do git logon dev, and if I follow the lines created git log --graph, I can trace this commit forward with a merge commit, where I combined my function branch with dev.
However, when I do a git blameof FILE-A, the commit does not exist, and the corresponding line is in the original (pre REV-Acommit).
In addition, the git show REV-A | patch -p1correction is applied cleanly. After that git diffit looks the same as git show REV-A.
What's happening? How is it that merging introduces revision into the history of branches, but does not actually apply it? Are there any other changes from this merge that are not applicable?
source
share