Unchanged files marked as changed after clone

Description

After cloning my repository from Github more or less all files are marked as “changed”. I suspect it has to do with line endings since no changes are visible in the Desktop application. The weird thing is “git status” reports no changes - and I would expect this to be the source of truth. I have tried setting core.autocrlf to true|false|input and clone the repository again - same result with either setting. It’s worht mentioning that binary files are marked as changed as well - for instance gradle-wrapper.jar. This issue sadly renders the Desktop app completely unusable for me.

Version

• GitHub Desktop: 1.2.3

• Operating system: Windows 10 64bit

Steps to Reproduce

Unfortunately my repo is within a closed organizational account so I can’t provide access to the exact repo. The steps to reproduce however are:

1. Clone repo
2. Check status of “git status” and verify that all files are up-to-date
3. Open Github desktop and add the newly cloned repo
4. Verify that almost all files are reported as changed without and diff

Expected Behavior

Github Desktop should report the same as “git status”

Actual Behavior

Unchanged files are marked as changed in Github Desktop even though “git status” reports no changed files

Additional Information

As noted above I expect this to be related to line endings. There are many contributors to this repository and I cannot know which core.autoclrf setting they are using. They are all working from Windows based machines. Here is a screen shot from Github Desktop illustrating the problem along with a commandline status:

Logs

2018-06-18.desktop.production.log

[chrstphrchvz]

I think core.filemode=true might be the culprit here (i.e. try running git config core.filemode false). I don’t know how that gets set by default, but looking online it seems to often be a problem Cygwin git users.

[steveward]

@hoof setting core.filemode to false will force Git to ignore file mode changes. The default setting is true when core.filemode is not specified in the config file.

Did setting this value to false fix the issue for you?