'git merge' 和 'git rebase'的区别?

最新推荐文章于 2025-09-23 06:16:15 发布

转载最新推荐文章于 2025-09-23 06:16:15 发布 · 515 阅读

版本管理工具专栏收录该内容

1 篇文章

订阅专栏

本文详细解释了Git中Merge和Rebase两种合并方式的原理、优缺点及使用场景，帮助开发者更好地解决代码冲突问题。

Suppose originally there were 3 commits, A,B,C:

A-B-C

Then developer Dan created commit D, and developer Ed created commit E:

A-B-C-D-E

Obviously, this conflict should be resolved somehow. For this, there are 2 ways:

MERGE:

A-B-C-D-E-M

Both commits D and E are still here, but we create merge commit M that inherits changes from both D and E. However, this creates diamond shape, which many people find very confusing.

REBASE:

A-B-C-D-E-R

We create commit R, which actual file content is identical to that of merge commit M above. But, we get rid of commit E, like it never existed (denoted by dots - vanishing line). Because of this obliteration, E should be local to developer Ed and should have never been pushed to any other repository. Advantage of rebase is that diamond shape is avoided, and history stays nice straight line - most developers love that!

转自：Stackoverflow

PS：老是觉得国外技术人员的解答更形象易懂一点。