-
Notifications
You must be signed in to change notification settings - Fork 426
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
v3 -> v4 exechook-command permission error #807
Comments
First, thank you for a complete repro, including a public repo. This does seem to be a use-case that is not covered by So the question then is how best to fix this. The easiest and most correct fix would be for you to make the file executable and for me to document this as a change. I suspect there's not a lot of people doing this. The more comprehensive fix would be to bring back some form of change-permissions flag. I didn' much like that old flag because it was too broad, but it did cover this specific case. I'm leaning towards "please change your repo", but would like ot hear counter-arguments. I'll have a think about how to expose this. |
Thank you for letting me know. I want to include the code and shell script in the repository, and perform post-processing with a shell script after syncing with the repository. It seems like '--group-write' won't work for this use case, so I'll explore other methods. |
Fundamentally you are trying to execute a file (your script) which is not executable. You can make it executable and check it in. Then git-sync should work. |
Did this solution work for you? |
Thanks a lot! I've converted it to 'hello.out' as an executable, and it works well. Now I'll update it to version 4. 👍 |
Hello.
I'm in the process of raising my version from 3 to 4 and have noticed a permission error. Everything else works fine, but when I run shell script with
exechook-command
it says permission denied. I thoughtgroup-write
would work likechange-permissions=0744
. So I'm wondering if there's bug or I'm mis-using git-sync.error log
v3.3.4, This works well.
v4.0.0, This isn't working
The text was updated successfully, but these errors were encountered: