Try: git config core.fileMode false. From git-config(1): core.fileMode Tells Git if the executable bit of files in the working tree is to be honored.
Git Tracks ONLY the Executable Bit of the Permissions for the User Who Owns the File. · Other permissions (write and read) for the file's owner are not tracked · All ...
By default, git will update execute file permissions if you change them. It will not change or track any other permissions. If you don't see any ...
Git tracks exactly one bit of permission: executable or not executable. You don't say what you mean precisely by "it stopped taking file ...
If you have noticed that git automatically tracks the changes in your file, take a look at this tutorial that shows you how to prevent it if you don't ...
I've read that git only tracks the executable bit of permissions, so I'm not sure why permissions would change when deploying. How can I automatically set ...
You can include a config file from another by setting the special include.path (or ... Core variables [core] ; Don't trust file modes filemode = false # Our diff ...
Git then regards all files as changed because their permissions are different.
If -v is specified twice, then also show the changes in the working tree that have not yet been staged ( i.e., like
For this, you can try the following command. git config core.fileMode false. Please refer to core.fileMode documentation: ...