git - How do you resolve a GitHub merge conflict that appears to have everything merged in? -


the repo contributing uses forking/rebasing pattern on github. feel i'm missing concept here did not result expecting. currently, pr says can't merge because there conflict, however, there appears no commits in dev branch don't exist in mine.

the steps took end here follows:

  1. created fork of repo
  2. created branch feature based on dev
  3. made changes, committed files
  4. created pull request

at point, got following error appveyor message:

this pull request contains merge conflicts must resolved. 

the recommendation "pull latest dev, rebase pr on it."

so, branch did following 2 commands update upstream (aspnet) , rebase branch off of dev:

git fetch aspnet git rebase aspnet/dev 

i expected branch contain of commits aspnet/dev, commits. instead, changes seem appear twice, other commit has appears in between them (so...there nothing left merge), have no conflicts locally , i've landed in following state:

graph of commits

now, changes aren't huge - limited single file - , nuke prs , start over, want understand did wrong , "correct" way have been it.

this pr in question: #24 refactored clearing of secrets file

is there way fix have pr can merge?

is there better flow follow rebase works correctly?

okay, there couple of things had do.

first, aspnet/dev , forked dev not in sync. them sync'd did following:

git fetch aspnet git checkout dev git rebase aspnet/dev git push 

next switched branch , cleaned things up, followed forced push repo/pr:

git checkout misterjames/clear-corrupt-secrets git rebase -i dev git push -f 

i squashed commits single commit during interactive rebase.

thanks @david-paquette tips on solving this.


Comments

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

linux - disk space limitation when creating war file -

How to provide Authorization & Authentication using Asp.net, C#? -