How to handle 422 errors (fork PRs coverage?)

Hey Coveralls team,

We are having an issue on our OSS projects Badger & Dgraph with coveralls. The error message is as follows:

Run goveralls -coverprofile=cover.out
bad response status from coveralls: 422
{"message":"Couldn't find a repository matching this job.","error":true}
Error: Process completed with exit code 1.

We have noticed that this happens at random. We have mostly seen this happening on contributions from outside authors from their forks. Internal author contributions via branch/PR seems to work fine. Would it be possible to get a little help here?

Our workflows use GitHub Actions, and are available here & here

Some sample errors include (mostly from outside authors' PRs):

The failed jobs in those links all have the same error message as above. Looking forward to your help & guidance here.

What we have tried:

resetting the token https://github.com/dgraph-io/badger/pull/1849#issuecomment-1402455920
read up other similar issues https://github.com/dgraph-io/badger/pull/1849#issuecomment-1402475775
force the service flag to GitHub https://github.com/dgraph-io/badger/pull/1849/files#diff-979eaac98bd181c1c298401668d7a399a75c136b92aa922b4a124d81b41ed534R39

cc: @joshua-goldstein

lemurheavy / coveralls-public

How to handle 422 errors (fork PRs coverage?) #1695