Closed joaocasarin closed 1 year ago
The same error happens if I try using v1.1.2
:
This action doesn't use the coveralls secret, but rather literally this:
github-token: ${{ secrets.GITHUB_TOKEN }}
Took me a while too to figure it out. Just copy-paste this literally in your ci.yml.
See: https://github.com/lemurheavy/coveralls-public/issues/1627
This action doesn't use the coveralls secret, but rather literally this:
github-token: ${{ secrets.GITHUB_TOKEN }}
Took me a while too to figure it out. Just copy-paste this literally in your ci.yml.
WOW! that was exactly the issue, their docs is not that clear, but now I get it... Thanks for sharing both the info and another issue that was raised regarding this.
Thanks, my friend!
I have just configured this repo to use coveralls actions as a coverage badge, created the secret as in the image below:![image](https://user-images.githubusercontent.com/48847394/195901732-353edcbc-82ab-48b5-a07d-eaf8f6839eba.png)
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...