About 217,000 results
Open links in new tab
  1. Git: Find the most recent common ancestor of two branches

    Oct 10, 2009 · The obvious-but-wrong git merge-base branch1 branch2 branch3 will give you a commit, but, as described in the Discussion section in the docs, it isn't necessarily a common ancestor of all …

  2. Why does git merge need a merge base? - Stack Overflow

    Jul 29, 2022 · Find diff between the target branch and the merge base Combine the two diff's from steps 2 and 3 I wonder why git merge doesn't directly find the diff between the current branch and the …

  3. git - How can I tell if one commit is a descendant of another commit ...

    Jun 9, 2010 · Using git rev-list like in VonC answer is also possibility. Edit: in modern Git there is explicit support for this query in the form of git merge-base --is-ancestor. If one of commits you are asking …

  4. How to fix git merge-base failing? - Stack Overflow

    Jun 8, 2024 · The git merge-base command is failing and returning nothing--no error or anything. The branch was created off of the dev branch, so there is a common commit between the two.

  5. In a git merge conflict, what are the BACKUP, BASE, LOCAL, and …

    Dec 4, 2013 · Git performs a three-way merge, finding the common ancestor (aka "merge base") of the two branches you are merging. When you invoke git mergetool on a conflict, it will produce these …

  6. git - How can I tell if one commit is an ancestor of another commit (or ...

    Use git merge-base --is-ancestor <commit1> <commit2> There is more than one way to find the answer to this. The simplest is to use git merge-base --is-ancestor <possible-ancestor-commit> <commit> …

  7. How to use git merge-base on remote? - Stack Overflow

    Jul 28, 2014 · The documentation contains no clue, wether the use of merge-base with ls-remote is possible. Maybe it is also possible, to use alternatives to merge-base to find the common ancestor …

  8. Github Actions: Git diff master...HEAD fatal: no merge base

    Nov 22, 2020 · 21 If you want to explore the history of master and HEAD (as in : find the merge base for these two commits), you can't limit your clone/fetch actions to a shallow clone -- not with depth=1 at …

  9. Is there a quick way to "git diff" from the point or branch origin?

    Apr 23, 2015 · 98 You can find the branch point using git merge-base. Consider master the mainline and dev the branch whose history you are interested in. To find the point at which dev was branched from …

  10. What is `git merge` doing? - Stack Overflow

    The git-merge man page and the git-merge-base man pages that you point out discuss multiple common ancestors and recursive merge. I feel that your answer is incomplete without a discussion of such.