James Kessler

Hi, @thoni56. I noticed that you aren't sending coverage to coveralls.io for your **pull_request** builds, [only **push** builds](https://coveralls.io/repos/271252/builds?page=1). Is there a reason for that? I ask because I think you'll...

Hi, @thoni56. Ok, I see. You're right. "PR builds" only work for builds that come to us with "genuine" PR info, from Github for instance, like `PR#`. You're also right,...

Good to know. Thanks.

@v0vanec you're correct, currently those levels (and colors) are hard-coded. There’s no way to change them at this time. But there is a somewhat longstanding feature request for this, for...

Hi @rivy. This feature request precedes me, but I have created a new card for it in our backlog and linked it to [this issue](https://github.com/lemurheavy/coveralls-public/issues/613) and other, potentially similar requests....

@rsharma02-entrata I will need some more information to help: 1. The Coveralls URL for your project 2. Any Build URL(s) showing the issue 3. The name of the Coveralls integration...

Thanks, @rsharma02-entrata. Received and replied.

Hi, @ylavoie. 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 as we possibly can....

Hi @ylavoie, Since [your **pull_request** build](https://coveralls.io/builds/52317710) showed correct coverage % after I re-ran it, I'm assuming you're experiencing a known issue mentioned in several other recent issues, but described below....

**NOTE**: In case you're having trouble determining what `build_num` is for your project, I posted some follow-up [here](https://github.com/lemurheavy/coveralls-public/issues/1631#issuecomment-1251722073). If you're using a different Coveralls integration and/or are still having trouble...