Error: The commit wasn't found on the repo about node-coveralls

[benpetty]

@derekherman I'm having the same issue using Travis-Pro. It's getting a commit hash that doesn't even exist in our repository. Where $TRAVIS_COMMIT is 50e440c5e3ec182607cb71370173cd884f33bc2a the response from coveralls is:

Bad response: 422 {"message":"The commit 0023214bdfc259bef2a8e00444f77fa60825a5ba wasn't found on the repo OrgName/RepoNameThe commit 0023214bdfc259bef2a8e00444f77fa60825a5ba wasn't found on the repo OrgName/RepoName","error":true}

As you can see the commit hash is wrong, is not even in our repo:

$ git show 0023214bdfc259bef2a8e00444f77fa60825a5ba
fatal: bad object 0023214bdfc259bef2a8e00444f77fa60825a5ba

The above config includes $COVERALLS_REPO_TOKEN environment variable being sent to travis. If I remove $COVERALLS_REPO_TOKEN, I get this:

Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

Even though the docs say this will work out of the box without it. I suppose it hasn't been tested for Travis-PRO or maybe something in Travis PRO has changed since the code was written.

I've submitted a PR that would definitely fix this. Instead of passing "HEAD", pass the actual $TRAVIS_COMMIT env var which will always exist in every travis build (pro/free).

Pull request here: #272

Someone please merge this and release!