Coveralls 422: `Couldn't find a repository matching this job. `

547 Views Asked by At

I have just configured this repo to use coveralls actions as a coverage badge, created the secret as in the image below: enter image description here

And as you can see in here, I am using the correct secret.

However, everytime I run this job I get the response Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

I have no idea what to do. I already checked in the coveralls website and the repo is fine... I noticed that github secrets page updated, and neither Coveralls nor Github documentation updated as well, the Coveralls docs is actually useless, it does not help in nothing regarding github.

1

There are 1 best solutions below

0
James On

Just wanted to mention that your fix was correct because, of all Coveralls integrations, the Coveralls Github Action is the only one that uses a token other than the Coveralls Repo Token to identify the repo to the Coveralls API. Since ${{ secrets.GITHUB_TOKEN }} is available from the Action itself, it is meant to be a faster, more convenient way to configure your integration with Coveralls.

As it may help, some more information on Coveralls integrations:

  1. Coveralls has 30+ community-created language integrations.
  2. Coveralls has three official "integrations": One integration, the Universal Coverage Reporter, and two (2) CI Service extensions, which use the Coverage Reporter as their underlying integration (since v2.0 of each): the Coveralls Github Action & the Coveralls Orb for CircleCI.
  3. The Coverage Reporter is their future direction for all official integrations and where they are continuing to add official support for new coverage report formats and new CI services.
  4. The Coverage Reporter README includes fairly simple instructions, with checklists, for developers to add support for more coverage report formats and additional CI services, for which Coveralls will compensate you with a free month of service.