Menu
Our workflow is develop on a local machine, commit the changes to a central repository, then check out the branch of that repository that we need.
The problem is that Git changes ownership and even file permissions of the files that it checks out, depending on the user making the checkout. A direct result of this is that our CSS files become unreadable after a checkout, as Git changes the file ownership to the person who did the Git pull in the webroot.
Example:
git pull: style.css owned by user_a:group_a git pull: style.css owned by user_b:user_b I want to keep ownership as user_a:group_a. I don't want to have to log in every time one of my team has made a change to the files, and change the ownership back to the original configuration.
How do other people deal with this? How do you deal with repositories used by multiple users. We have suphp on our system and cannot take it off.
364
Git tracks exactly one bit of permission: executable or not executable. You don't say what you mean precisely by "it stopped taking file permission changes into account", but my best guess is that you didn't change the executable permission, and so from Git's point of view, there was no change to take into account.
Set the Appropriate Permissions on Objects Directory Make sure all your users who need access to git are part of the git group. Change the “git” in the above chgrp command to whatever group where all your developers belong to. The “s” option in the “g+rws” is to set the setuid bit on the objects folder.
Show activity on this post. I know git does not store file permissions, and I am not expecting to remember permissions when creating new file.
According to kernel.org git does not store all the permissions possible for files. Git is a content tracker, where content is de facto defined as "whatever is relevant to the state of a typical sourcecode tree". Basically, this is just files' data and "executable" attribute.
Git does not change file permissions or ownership. It's just that it (mostly) doesn't store it either, it doesn't exist in your repo, so they get changed to whatever your user has. Just like with any file creation.
Git supports two permission sets: executable bit on and executable bit off. Nothing else. Ownership information is not stored at all.
See this thread - "If you want specific permissions, you'll need to do it manually."
There are some solutions suggested: you can use a separate tool to do it for you, use a proper combination of user account and umask to set them properly by default or write a git hook yourself to do it. A hook would've to be installed on the user doing the checkout.
Like @ikke said in the comments, Git is not really a deployment tool and should not be used as such. It is a version control system for source code.
129
For me, the best solution was creation of a shell script that fixes the permissions. For example:
.git/hooks/post-checkout: #!/bin/sh chmod +x tools/* Btw, checkout is not the only case when git does mess with permissions, it's also when you pull. I handle that with .git/hooks/post-merge hook.
Ideally, you can create a shell script that fixes permissions somewhere in your repo (e.g. tools/fixpermissions.sh), and call it in both hooks. Don't forget to change the permissions for that file manually ;)
#!/bin/sh chmod a+x tools/fixpermissions.sh tools/fixpermissions.sh If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
