James Kessler

Hi @xcelerit-dev. Thanks for reporting your issue. This is something that's been happening lately, for a handful of repos as far as we know ([example 1](https://github.com/lemurheavy/coveralls-public/issues/1632) | [example 2](https://github.com/lemurheavy/coveralls-public/issues/1631)). Specifically,...

Ok, it turns out I was wrong. You were not the owner of your repo. You were the only _user_ of the repo, but your repo _had_ no owner. I...

Yes, I'm sorry to say, you're squarely in the pattern of this known but currently unresolved issue. Just to make sure, using this PR build as a test: https://coveralls.io/builds/51200176 ![Screen...

Hi, @OndraM. Thanks for the report. It sounds like we'll need to add you to this issue. Which I'll do as soon as I'm able to verify and make sure...

@xcelerit-dev @OndraM @Torgen ## Workaround for this issue: the Rerun Build Webhook While we've not yet identified a fix for this issue, we released a workaround today that should resolve...

@xcelerit-dev apologies. I forgot that some Coveralls integrations (like the Coveralls GitHub Action) have special features around the (Close) Parallel Build Webhook, such that you don't need to build the...

@gzoller @ruippeixotog @carueda The task of integrating a scala project with coveralls can almost certainly be accomplished, but it looks like the community-created integration we're aware of, [sbt-coverage](https://github.com/scoverage/sbt-scoverage) with [sbt-coveralls](https://github.com/scoverage/sbt-coveralls/issues/125),...

Hi @fingolfin, the specific values for `service_name` depend on what integration you're using and whether that integration supports the particular CI service. This is a result of there being many...

Hi @ddold. Strongly agree that `CIRCLE_BUILD_NUM` works better as build number than `CIRCLE_WORKFLOW_ID`. To complete your PR we'd need to make an accompanying change to [node-coveralls here](https://github.com/nickmerwin/node-coveralls/blob/21f7b1da017e1b2386b4354a0d8345937294fd26/lib/getOptions.js#L57-L58) to make the...

Hi @ddold. Thanks for creating that [issue](https://github.com/nickmerwin/node-coveralls/issues/323) and including a reference to the [code](https://github.com/nickmerwin/node-coveralls/blob/21f7b1da017e1b2386b4354a0d8345937294fd26/lib/getOptions.js#L57-L58). So I was able to reproduce the issue with the sync branches button. It's a bug....