version control - Git rebase: finding the "next" commit to be rebased? -



version control - Git rebase: finding the "next" commit to be rebased? -

we have 2 branches in git, master , develop. master beingness updated partner group, , rebasing our develop branch onto master, this:

#(on develop) $ git pull --rebase origin master #1 $ git rebase origin/develop #2 $ git force origin develop #3

…but yesterday partner grouping committed onto master without proper e-mail address, , encounter problem step #2:

git rebase origin/develop first, rewinding head replay work on top of it... applying: <...> <...> patch not have valid e-mail address.

and git status shows:

$ git status # not on branch. # rebasing. # (all conflicts fixed: run "git rebase --continue") # nil commit, working directory clean

what have done skip commits without address git rebase --skip, cherry-pick these commits after rebase. wonder proper way it? can cherry-pick commit in question straight in-place, without skip it? if yes, how find out problematic commit (without looking in git log), quasi next commit rebased on top of current commit, git must somehow knows 1 is…?

you can seek suggestions in change author of commit in git

or can add together -i in there maintain going (useful if have persistent auto-tooling commit issue or want maintain going , allow else prepare problem eventually)

so, when

> git rebase master first, rewinding head replay work on top of it... patch not have valid e-mail address.

i git rebase --abort, , then

> git rebase master -i rebased , updated refs/heads/mybranch.

this true git 2.1.4.

obviously, comes rebase list edit, save unedited , go on way.

and yes, commits "original author <>"

git version-control git-rebase

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -