James Kessler

Hi, @mitchell-codaio. Thanks for the report. We're experiencing an extremely high volume of support requests this week and are working through a backlog. We'll respond to your issue as soon...

@OndraM @jrfnl @ylavoie @guy-yogev-lmnd Sorry for the delay in getting back to this issue. Thanks for your patience. I am checking each referenced build and will reply in kind momentarily.

@OndraM, > Hi, shouldn't `repo_token` be the value which is displayed on coveralls repository homepage (when signed in), instead of `GITHUB_TOKEN`? Yes. That's correct. Sorry if I mislead your or...

@jrfnl: >> But then how is Github Action supposed to find that repo-token? > > In that case, each user should add the repo token from Coveralls to their repo/organisation...

@ylavoie: > > In that case, each user should add the repo token from Coveralls to their repo/organisation "secrets" (Settings -> Secrets -> Actions) and then refer to the secret...

@jrfnl: > > I think I know what the issue may be and will try to fix it and re-deploy today. I will let you know here. > > @afinetooth...

@guy-yogev-lmnd: > @afinetooth, any updates on this issue? This issue makes Coveralls pretty misleading in our teams PR's I understand completely. Can you please share the Coveralls URL(s) for the...

Hi @bastelfreak. (Cc: @mrexox) Hoping this will resolve any questions of support you have for a Ruby-based Coveralls Integration: **tl;dr**: Please try [coveralls-ruby-reborn](https://github.com/tagliala/coveralls-ruby-reborn), which is a more up-to-date fork of...

@elliotwutingfeng thanks for the workaround. @kbrandwijk in case that doesn't help you, can you help me with what the exact scenario is that results in the coveralls badge not being...

Hi @alanmcruickshank. The issue is that your repo is missing an owner. We leverage the OAuth token of the repo "owner," typically the user who added the repo to Coveralls.io,...