Replies: 3 comments 2 replies
-
Thanks for the detailed logs! |
Beta Was this translation helpful? Give feedback.
-
I have now and I get the same result. I'm thinking this may have something to do with the way that the pre-receive environment is isolated and set up to contain the new objects (which are not kept if it fails) but I can't find any documentation on that. |
Beta Was this translation helpful? Give feedback.
-
I think it would be good to know the gitpython version in use here. Furthermore you could add this to the bash script:
I have the feeling the git directory is a file. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure if this is an issue with GitPython or not but I'm reporting it here in case it is and in the hope you can shed some light on the problem.
I am developing an application that uses a pre-receive hook. The hook needs to generate a map of the added/modified/deleted files relating to the submitted change and, as I've used GitPython before it seemed natural to use it here. The pre-receive bash script dispatches to my code thus:
And the pre_receive looks something like this (stripped down to show the issue):
The error I get is:
When I invoke the same command in a shell on the same repository it works fine. Obviously I'll probably be using diff-tree etc. in the real application but this same error occurs whatever command I invoke, in spite of the fact that I can copy paste the command into the shell and it works:
Note that the shell was not running in the .git folder hence the slight tweak (left in to show that it would generate a different error anyway).
The logging debug log shows:
which presumably comes from GitPython and looks like it should end up doing the right thing.
Any idea what is going on?
Beta Was this translation helpful? Give feedback.
All reactions