-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chmod modifies git working directories in Islandora modules #78
Comments
Wouldn't 644 be the proper permission for files (except scripts)? It seems if someone wanted to override this for their own copy they could add it to their local git settings, but that the repo should be opinionated about default file permissions? |
Yes, the setting could be overridden locally on a repo-by-repo basis, but you'd have to do it on every module's repo. If that's OK, then there's no problem. |
How about setting |
Sure, if that would work. Want me to test? |
Sure |
I added
After I add the following to /home/vagrant/.gitconfig:
I can run
But if I run
I looked in a few module's .git/config files and they all contain a core.filemode = true setting. So setting it globally wouldn't work anyway since it's overridden at the repo level. Document as known issue? |
What if we did something like this: cd "$DRUPAL_HOME"/sites/all/modules
while read LINE; do
cd $LINE
git config core.filemode false
cd "$DRUPAL_HOME"/sites/all/modules
done < "$SHARED_DIR"/configs/islandora-module-list-sans-tuque.txt Right here. |
Closed with 63ceaf0 |
If you run
git status
in any of the Islandora module directories all files are indicated as 'modified'.git diff
shows that the difference is 'old mode 100644 / new mode 100755'.There is a
git config core.fileMode false
command that can nullify this behavior, but I can't find any evidence that it is configurable in .gitattributes, which would be the ideal place to tell git to ignore permission changes at the repo level. Runninggit config core.fileMode false
in each of the cloned repo's directory would have the same effect. Configuring this setting for the vagrant user or globally seems like overkill.The text was updated successfully, but these errors were encountered: