Another way to view it is that a rebase replays the changes in your target branch on top of the source branch history. In the preceding diagram, commit C is the last common commit in both branches. Git rebase resequences the commit history of the target branch so that it contains all source branch commits, followed by all target branch commits since the last common commit. In your branch's commit history, a merge commit is a useful marker for a merge operation, and clearly shows which branches were merged. The source and target branch tips (K and E) are the parents of the merge commit. The merge commit (L) contains the integrated source branch and target branch changes. If any source branch change conflicts with any target branch change, then Git will prompt you to resolve the merge conflict.
The applicable changes are those made after the last commit that's common to both branches.
#Sublime merge git log update
For example, Git will apply a fast-forward merge on a local branch that you only update by pulling from its remote counterpart branch.Ī no-fast-forward merge generates a new target branch "merge commit" that integrates source branch changes with target branch changes. By default, Git uses a fast-forward merge whenever possible. Otherwise, the default merge type will be a no-fast-forward merge.Ī fast-forward merge can never have a merge conflict because Git won't apply a fast-forward merge if the tip of the target branch has diverged from the source branch. These merge types are shown in the following diagram.įor Git merge, if the tip of the target branch exists within the source branch, the default merge type will be a fast-forward merge. The no-fast-forward merge is also known as a three-way merge or true merge. Git merge performs either a fast-forward or a no-fast-forward merge. Git merge or rebase integrates commits from a source branch into your current local branch (target branch).
0 kommentar(er)
