gitlab.com "remote: GitLab: API is not accessible" when git hooks are enabled
With the latest release, albeit, I recently signed up and testing the service, I am running into this error when pushing to a repository with Git Hooks enabled. Only after disabling all git hooks, does the commit go through.
$ git push origin bug-1002
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 288 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: GitLab: API is not accessible
To git@gitlab.com:XXXXXXXX/test.git
! [remote rejected] bug-1002 -> bug-1002 (pre-receive hook declined)
error: failed to push some refs to 'git@gitlab.com:XXXXXXXX/test.git'
Repro steps:
-
Enable "Check whether author is a GitLab user" in Git Hooks for a project
-
Specify a ruby regex (see above) for "Commit author's email" field (*@XXXXXXX.com$)
-
Push a commit with valid committer and author email.
Expected Results:
- GitLab should accept the commit
Actual Results:
- Results in "remote: GitLab: API is not accessible" error when pushing commits
Notes:
- The commit author email rule seems to work as trying to push up a commit from @domainfoo.com gets blocked with the right error.
- Unchecking #1 (closed) and keeping #2 (closed) produces API is not accessible error.
- Unchecking #2 (closed) and keeping #1 (closed) produces the same API is not accessible error