Git/GitKraken – File Mode changes to unknown value (14001) after restoring repo from backup

Question

Still new to Git(Kraken). Had a logic board go bad on me, and had to restore a repo from a backup, reinstall software, and get back up and running on a temporary machine till I can get the original back from the shop.

Now I have the repo open in Gitkraken, which is telling me I have 2,224 file changes on my hotfix branch – apparently all files. If I click on any one of them, the Diff View panel displays the messages, "File Mode Changes from 217 to 14001" and "File contents are unchanged."

I was able to translate the 217 Octal Value on file permissions.com, but found nothing for 14001.

I'm no expert on file permissions, but 217 (presumably the default setting on my prior machine, as I don't recall changing it) appears to be less than ideal, with only write access for User, execute access for Group, and full access for Other.

Can anyone tell me what this 14001 setting is all about (this is a brand new MacBook Pro, vs. the 2015 model that's being fixed)? Is this setting preferable to 217 (it would almost have to be...?)? What settings are ideal for static website files, and would it be good/bad/neutral to push these file mode changes?

Answer 1

I had the exact same problem where GitKraken shows "File Mode Changes from 217 to 14001." My teammate ran some command with sudo which changed the file modes. It may be a GitKraken bug – if you use git show -p <commit_hash> you'll see the actual change was " changed file mode from 100644 to 100755."

The permission 644 is -rw-r--r--, and 755 is -rwxr-xr-x. You'd want to keep the permissions as 644 as most files should not be executable.

You can either revert the commit, or use chmod stated in this answer.