-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always getting Error: Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true} #81
Comments
Same issue. |
hi @irverysmart and @lc-soft. for future reference, the more active resource for coveralls user support is here: that error usually indicates a missing or incorrect repo token for your project. that's usually avoided with our github action, because we're using the github_token secret, so this indicates some other key data is missing from the JSON you're POSTing to the coveralls API. to look further into this for you i'll need your coveralls project URLs. since they are private, you can email the info to support@coveralls.io and reference this issue. in the meantime, try setting this debug env var so your build logs reveal the underlying JSON you're about to send:
in your workflow file, like:
|
PS: I have no idea if point 2 is an bug/issue or is it an intended behavior but it fixed my issue. Maybe add it to the |
Trying to use a private repo with the github action using the following .yml:
this is the exact same .yml provided on https://github.com/coverallsapp/github-action as the "standard example" with
make test-coverage
swapped fornpm test -- --coverage
(to generate lcov.info).I've logged into the website and turned the repository "on" and I see the repository in the "my repos" tab, but still the action always fails with the following:
I'm kind of stumped, are there some better docs to take a look at or any working examples?
The text was updated successfully, but these errors were encountered: