Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalFor me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows gitGit client failed to reproduce. Solution
The solution for me was to tell gitGit to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows Git client failed to reproduce.
The solution for me was to tell Git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with MaxMac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Max/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?
For me, it had something to do with file permissions. Someone with Mac/Linux on my project seems to commit some files with non-default permissions which my Windows git client failed to reproduce. Solution for me was to tell git to ignore file permissions:
git config core.fileMode false Other insight: How do I make Git ignore file mode (chmod) changes?