James Kessler
James Kessler
@liskin @TheKevJames, re: > @nickmerwin Would you perhaps be able to shed some light on what's the difference between `github` and `github-actions` service names from the coveralls API point of...
@liskin, looking at it more closely, you're right, the job can get through with `null` for `service_job_id`. The reason I described it as "required" is because the [Coveralls Github Action](https://github.com/marketplace/actions/coveralls-github-action)...
@liskin thanks for the additional input here. Doing some local testing by forking the repo of my o.p., @zgoda, and may need some more examples, of which yours and @vchrombie's...
FYI, @TheKevJames, @liskin, I completed tests of [my own fork](https://github.com/afinetooth/flask-rollup) of @zgoda's [repo](https://github.com/zgoda/flask-rollup) following steps he described that continually reproduce the 422 error for him. As you can see from...
> I still think it's odd to put anything but the GITHUB_TOKEN into the env var called GITHUB_TOKEN. Putting the coveralls provided token in there seems very confusing for both...
> Oh, perhaps it does expose secrets when the PR is from the same repo. Mea culpa. All good! I'm having trouble finding a decisive answer on it. It seems...
Hi @TimoRoth, I guess I introduced the double-usage of `GITHUB_TOKEN` in my (limited) example to (ideally, temporarily) work around the 422 error described in [this issue](https://github.com/lemurheavy/coveralls-public/issues/1435#issuecomment-820706587). As I explain above,...
I'm ok with that but, personally, I'm just a support engineer so my goal is to help users get their builds sending coverage to coveralls and provide background on the...
I understand! it's been around for a long time and you guys have tried to work around it and a lack of documentation on it admirably. We're good. Hopefully we...
@rook2pawn i was just reviewing this before closing. i looked at your verbose output here: above:https://curlpaste.com/web/mnk7ge FWIW, the issue appears to be your repo_token. This is an unlikely value: ![Screen...