GIT creating extraneous ~HEAD files during rebase -
running issue i've never seen while rebasing.
i have master branch has had bugfixes.
i have dev branch forked off of master sometime in past, before bugfixes.
i change dev branch, run:
git rebase master it rewinds , tries replay dev changes.
the rebase stops, conflict have resolve.
i resolved normal conflict, added resolved file, run:
git rebase --continue there conflict, , run:
git status ..to see state of things. see normal changes, unmerged paths, untracked files i've never seen before:
path/to/something/existingfilename.ext~head i can , see these files did not exist in either branch @ time of commit reverted to. i'm curious why created rebase process, , what, if should them?
these files uses reconcile merge: yours, theirs, , thing both started with. after resolve conflict, , run git rebase --continue , done, still there?
Comments
Post a Comment