Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
893 views
in Technique[技术] by (71.8m points)

version control - Make git pull --rebase preserve merge commits

git pull --rebase removes unpushed merge commits. Is there a way to make it preserve them?

Say my history looks like—

A
|  
B  H
|  |
C  G
|  |
D  F
| /
E

(A being the merge commit.)

After a git pull --rebase it becomes—

H
|
G
|
F
|
X
|
B
|
C
|
D
|
E

(X being the new commits git pull --rebase inserted into my history.)—A is removed.

I know you can use git rebase --preserve-merges to preserve them with git rebase, but I don't see a way to preserve them with git pull --rebase.

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

Update: As I presented in "What exactly does Git's "rebase --preserve-merges" do (and why?)", since Git 2.18 (Q2 2018), you would prefer the new option --rebase-merges to the legacy one --preserve-merge

Since then:

So:

git rebase --interactive --rebase-merges origin/master 
# or
git config pull.rebase merges
git rebase --interactive origin/master (would use rebase-merges)

Original answer 2013:

Or (for the upcoming git 1.8.5 Q4 2013, now delivered in git 1.8.5, 2013-11-27):

"git pull --rebase" always chose to do the bog-standard flattening rebase.
You can tell it to run "rebase --preserve-merges" by setting "pull.rebase" configuration to "preserve".

So a simple config will be enough to make sure your pull --rebase does preserve merge:

git config pull.rebase preserve

See commit 66713ef3 for more (thanks to Stephen Haberman):

pull: allow pull to preserve merges when rebasing

If a user is working on master, and has merged in their feature branch, but now has to "git pull" because master moved, with pull.rebase their feature branch will be flattened into master.

This is because "git pull" currently does not know about rebase's preserve merges flag, which would avoid this behavior, as it would instead replay just the merge commit of the feature branch onto the new master, and not replay each individual commit in the feature branch.

Add a --rebase=preserve option, which will pass along --preserve-merges to rebase.

Also add 'preserve' to the allowed values for the pull.rebase config setting.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...