I have a project in which I have to change the mode of files with chmod to 777 while developing, but which should not change in the main repo.
Git picks up on chmod -R 777 . and marks all files as changed. Is there a way to make Git ignore mode changes that have been made to files?
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. Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary. A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1). The default is true (when core.filemode is not specified in the config file).
The -c flag can be used to set this option for one-off commands:
git -c core.fileMode=false diff Typing the -c core.fileMode=false can be bothersome and so you can set this flag for all Git repositories or just for one Git repository:
# This will set your the flag for your user for all Git repositories (modifies `$HOME/.gitconfig`) # WARNING: this will be overridden by the local configuration, and the fileMode value is automatically selected with the latest version of Git. # This means that if Git detects your current filesystem is compatible, it will set the local core.fileMode to true when you clone or init a repository. # A tool, like Cygwin emulation, will be detected as compatible, and so your local setting WILL BE SET to true, no matter what you set in the global setting. git config --global core.fileMode false # This will set the flag for one Git repository (modifies `$current_git_repo/.git/config`) git config core.fileMode false Additionally, git clone and git init explicitly set core.fileMode to true in the repository configuration as discussed in Git global core.fileMode false overridden locally on clone.
core.fileMode is not the best practice and should be used carefully. This setting only covers the executable bit of mode and never the read/write bits. In many cases, you think you need this setting, because you did something like chmod -R 777, making all your files executable. But in most projects, most files don't need and should not be executable for security reasons.
The proper way to solve this kind of situation is to handle folder and file permission separately, with something like:
find . -type d -exec chmod a+rwx {} \; # Make folders traversable and read/write find . -type f -exec chmod a+rw {} \; # Make files read/write If you do that, you'll never need to use core.fileMode, except in very rare environments.
git config --global core.filemode false you'll only need to do this once for all repos.
git config command writes the setting to the correct config file (.git/config for just the current repository, or ~/.gitconfig if used with --global).
Undo a mode change in the working tree:
git diff --summary | grep --color 'mode change 100755 => 100644' | cut -d' ' -f7- | xargs -d'\n' chmod +x git diff --summary | grep --color 'mode change 100644 => 100755' | cut -d' ' -f7- | xargs -d'\n' chmod -x Or in mingw-git:
git diff --summary | grep 'mode change 100755 => 100644' | cut -d' ' -f7- | xargs -e'\n' chmod +x git diff --summary | grep 'mode change 100644 => 100755' | cut -d' ' -f7- | xargs -e'\n' chmod -x Or in BSD/macOS
git diff --summary | grep --color 'mode change 100644 => 100755' | cut -d' ' -f7- | tr '\n' '\0' | xargs -0 chmod -x git diff --summary | grep --color 'mode change 100755 => 100644' | cut -d' ' -f7- | tr '\n' '\0' | xargs -0 chmod -x 
-d'\n' part from xargs as this is an illegal argument (and not needed).
tr '\n' '\0' and then use the -0 arg to xargs to use NUL as the delimiter.
tr thing worked! Here's the full command for OSX: git diff --summary | grep --color 'mode change 100644 => 100755' | cut -d' ' -f7-|tr '\n' '\0'|xargs -0 chmod -xIf you want to set this option for all of your repositories, use the --global option.
git config --global core.filemode false If this does not work, you are probably using a newer version of Git, so try the --add option.
git config --add --global core.filemode false If you run it without the --global option and your working directory is not a repository, you'll get
error: could not lock config file .git/config: No such file or directory
--add, as in git config --add --global core.filemode false
If
git config --global core.filemode false does not work for you, do it manually:
cd into yourLovelyProject folder cd into the .git folder:
cd .git Edit the configuration file:
nano config Change "true" to "false":
[core] repositoryformatversion = 0 filemode = true ->
[core] repositoryformatversion = 0 filemode = false Save, exit, and go to the upper folder:
cd .. Reinit the Git instance:
git init You are done!
.git/config, a simple git config core.fileMode false in the root of your project is enough. If you edit the config file, you're better of removing the directive entirely, so that the global one is picked up.
global option does exactly the same thing as manually editing .git/config
~/.gitconfig, and ~/project/.git/config)
git init should we set filemode back to true?
git init returns filemode back to TRUE!Adding to Greg Hewgill's answer (of using the core.fileMode config variable):
You can use the --chmod=(-|+)x option of git update-index (a low-level version of "git add") to change execute permissions in the index, from where it would be picked up if you use "git commit" (and not "git commit -a").
You can configure it globally:
git config --global core.filemode false
If the above doesn't work for you, the reason might be your local configuration overrides the global configuration.
Remove your local configuration to make the global configuration take effect:
git config --unset core.filemode
Alternatively, you could change your local configuration to the right value:
git config core.filemode false
git config -l (list current config - both local and global)
If you have used the chmod command already, then check the difference of the file. It shows the previous file mode and the current file mode, such as:
new mode: 755
old mode: 644
Set the old mode of all files using the below command:
sudo chmod 644 . Now set core.fileMode to false in the configuration file, either using a command or manually.
git config core.fileMode false Then apply the chmod command to change the permissions of all files, such as:
sudo chmod 755 . And again set core.fileMode to true.
git config core.fileMode true For best practises, don't keep core.fileMode at false always.
For best practises don't Keep core.fileMode false always what do you mean, you should explain that.
For best practises don't Keep core.fileMode false always. Some filesystems (FAT for example) don't support file permissions, so the OS will report a default value (766 on my system anyway). In this case, core.filemode is absolutely necessary in the local config, unless you want to bloat the commit history with unnecessary and unintentional permission changescore.filemode=false then git will ignore execute bit changes, no need to change local permissions. Unless you've already added permission changes to the index, in which case you're missing the step where you would need to git add after you turn off core.filemode.By defining the following alias (in file ~/.gitconfig), you can easily temporarily disable the fileMode per the Git command:
[alias] nfm = "!f(){ git -c core.fileMode=false $@; };f" When this alias is prefixed to the Git command, the file mode changes won't show up with commands that would otherwise show them. For example:
git nfm status 
If you want to set filemode to false in configuration files recursively (including submodules):
find -name config | xargs sed -i -e 's/filemode = true/filemode = false/' 
git submodule foreach git config core.fileMode falseA simple solution:
Hit this simple command in the project folder (it won't remove your original changes); it will only remove changes that had been done while you changed the project folder permissions.
The command is below:
git config core.fileMode false Why this all unnecessary file get modified: because you have changed the project folder permissions with command
sudo chmod -R 777 ./yourProjectFolder When will you check changes what not you did? You found like the below while using git diff filename:
old mode 100644 new mode 100755 
You don't need to change the configuration file.
Just run:
git diff -G. Note that the trailing dot is not at the end of the sentence, but a regular expression expression that matches everything and must be included.
This works for me:
find . -type f -exec chmod a-x {} \; Or the reverse, depending on your operating system:
find . -type f -exec chmod a+x {} \; 
git diff, and who therefore does not want to alter their Git configuration files: you can usegit diff -G.per Zed's answer here.