Git merge: Difference between revisions
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
git checkout < | git checkout <base-branch> | ||
git merge < | git merge <head-branch> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 19:55, 5 September 2022
Internal
Overview
git checkout <base-branch>
git merge <head-branch>
By default, merge creates a merge commit.
However, if the branch we're merging from contains only extra commits, and the branch we are on does not contain commits that are not in the branch we're merging from, git merge will automatically fast forward without specifying anything. This is the case when, after a git fetch, the origin branch advances with new commits and our local tracking branch is clean. In this case we can fast forward with:
git checkout <tracking-branch> git merge origin/<tracking-branch>
Options
--no-ff
Create a merge commit even when the merge resolves as a fast-forward. This is the default behaviour when merging an annotated tag. This is also the default behavior when merging GitHub pull requests with "Create a merge commit" option.
Troubleshooting
If 'git merge' produces this error message:
fatal: No remote for the current branch.
it's probably because the local branch has not been linked to its remote-tracking branch. Fix with: