version control - Moved a git repo - now every file has an unstaged change.. (permissions?) -
i've been working on repo making commits - went well. decided move repo in directory allow me use on local server. (i use virtual hosts still prefer keeping virtual-hosts linked specific sub directories)
after moving files (plain mv
on os x) had change permissions app work on system, good..
then went commit changes... every file has unstaged changes. when cloned remote in directory try , compare differences.. repo has unstaged changes on every file.
the repo fine before moved it, , cloned new 1 displaying peculiar behaviour; .git
file can't corrupt. thing can think of changing permissions, did new repo too.
could changing permissions on directory have caused this? haven't had happen before, it's thing can think of. if so, there easy way of resolving this? it's bit of nightmare right now.
i've seen 1 other similar question, doesn't appear same: sometimes git tells me every new file new , unstaged. answer question appeared users of different operating systems working on same repo, , line endings causing issues. in scenario, both developers using os x.
depending on changes made permissions can indeed issue. while git ignore permissions does track whether or not file should executable.
whatever differences exist should shown git diff
.
since in answer git diff shows:
old mode 100644 new mode 100755
that shows issue indeed permissions. git told files should not executable, files in working tree have executable bit set.
you you've worked around issue setting core.filemode
false, wouldn't recommend that. instead i'd suggest either removing execute permission whatever files don't need or commit changes permissions.
Comments
Post a Comment