version control - Why does git-pull "repo location" take the working directory changes? -
i have local repo working copy in dir , clone parallel dir b. switch branch in a, make changes, , commit them. if go b , "git pull ../a" changes active branch applied master in b... not expecting. if "git pull" relying on configured origin not happen of course.
is expected behavior of git-pull "repo location" when there working copy? can point me documentation describes this?
edit: assumed must basic git behavior / use case didn't know far i'm not getting responses question. in case wondering why - work on own projects local git repos on multiple machines. thought git way pull changes between them needed , doing on ssh directly between folders... not expecting pulling changes affected working copy happened checked out in remote repo. i'm not sure how can avoid mistakes using technique in future. must commit changes bare repo in order share them?
it seems git pull respects locally checked out branch fetching , merging changes same remote repo branch, git pull ../a takes whatever checked out in remote working copy , merges local working copy... not have custom configuration, test creating empty dir, initializing repo, adding file, branching , cloning described in op. post exact sequence of instructions if needed. guess i'm resolved does.
Comments
Post a Comment