git - How to fix a commit accidentally marked as merge on SourceTree? -


sourcetree/bitbucket/git question: trying merge master branch feature branch in sourcetree, conflict detected. sourcetree downloaded , staged changes master branch , left me conflicted file fix. however, when resolving conflict, realized need make more changes file - so, unstaged files master branch , discarded changes in them, made modification in 1 remaining file , staged few lines , made commit. but, sourcetree still classified merge commit, it's marked such on bitbucket, despite fact commit merely changed few lines in 1 file , none of changes master branch included.

the real problem when i'm trying merge master feature now, sourcetree says branch 'already up-to-date', despite fact not, , can see on diff tab on bitbucket. apparently, bitbucket thinks merged previous commit, although wasn't. how can fix situation?

it seems mix when resolving conflict. want merge master branch feature branch? if yes, should select feature branch current branch, , click merge -> pick commit on master branch.

when merge conflict appears, current branch still feature, show errors if switch master branch before resolving conflict.

if want make more changes before resolving conflict, should unstage -> discard file -> switch master branch -> make more changes -> commit.

after update master branch -> switch feature current branch -> merge -> pick commit on master branch -> resolve conflict.


Comments

Popular posts from this blog

php - How to add and update images or image url in Volusion using Volusion API -

javascript - jQuery UI Splitter/Resizable for unlimited amount of columns -

javascript - IE9 error '$'is not defined -