In a bash script, git does not recognize it own directory?

Question

So I have written a bash script within Atlassian-Stash for post-receive events. In this script, after a commit has been made, it creates a codecollaborator code review. To create a code review, it needs commit title, commit user and git SHA for any changes and uploading the changes to the code review. To get these informations, I clone'd the directory to --depth=1 (even without --depth=1) and work with git log (options). The problem I am seeing is that if I run the script manually, it works just fine. However, if it runs after a commit has been made, it errors out after it clones the directory saying it is not a git directory. If I cd into the directory after the script exits, I am able to run git log (and other git commands). Things I tried to troubleshoot are 1. Permissions issues (running it as root), so I am not seeing any permissions issues. 2. troubleshooting it with bash -xv and until that point everything looks good. 3. I also put it status checks with $? 4. I tried to move .g…

Accepted Answer

I know nothing about Atlassian but it's clear from the error output that you're tripping over one of the hook traps I noted in an answer I can't find now:

- In a git hook, the environment variable `GIT_DIR` is set (to `.` in `--bare` repos, to `.git` in non-bare ones). This is valid only until you `cd` to some other directory, often in a sub-process run from the hook script that has no idea that `$GIT_DIR` is pointing off to some now-inappropriate place.

(The `git clone` step works because it is not looking for a git directory, it's just creating a new one.)

The quick and easy fix is `unset GIT_DIR`.

In a bash script, git does not recognize it own directory?

Solution

Problem