version control - Cleaning up after a conflicted git merge? -


i had small conflict in .h header file in project i'm working on. project tracked in git.

fortunately, conflict simple solve. used

git mergetool

and chose default (opendiff) seemed filemerge on mac. made appropriate changes, saved file, , closed.

git asked me if merge successful, said yes:

was merge successful? [y/n] y

but now, have:

> git st # on branch develop # changes committed: #   modified:   myheader.h # # untracked files: #   (use "git add <file>..." include in committed) # #   myheader.h.backup.52920.h #   myheader.h.base.52920.h #   myheader.h.local.52920.h #   myheader.h.remote.52920.h #   myheader.h.orig 

which of junk conflict files created filemerge, , git?

and more importantly: how remove them?

you can delete them other file. example:

rm myheader.h.orig 

alternatively, if there no other untracked files, after commit with

git commit -a 

you may clean repository with

git clean -n git clean -f 

git clean -n tell git clean -f do, can sure it's want.


Comments

Popular posts from this blog

c - How to retrieve a variable from the Apache configuration inside the module? -

c# - Constructor arguments cannot be passed for interface mocks -

python - malformed header from script index.py Bad header -