James Kessler

@EvHaus: Well, one way to make sure you're getting the head of the current branch is to do a: ``` git checkout ``` in your CI config before the step...

Thanks @CyberShadow I've reproduced and reported this.

@jrfnl May I re-process the jobs in your parallel build to make sure this is not a one-off issue? This will re-consume each of your coverage reports as they came...

@jrfnl some quick updates: On this **PR build**, mentioned above: https://coveralls.io/builds/48166327 I re-ran the jobs in the **PR build** and got a different result—specifically, the small _increase_ in coverage you'd...

@jrfnl, Ok, thanks for the update. I understand your concern better now, so I'll stay focused on the aggregate coverage and let the job-to-job comparison be secondary. In fact, as...

To see if it clears the issue, we could run a quick test, _without_ using the [Coveralls Github Action](https://github.com/marketplace/actions/coveralls-github-action). That would mean sending the [Parallel Build Webhook](https://docs.coveralls.io/parallel-build-webhook) in your final...

@jrfnl thanks for the update: > [...] The documentation on this is sparse, to say it in the most polite way possible. Appreciate that. You're right. We've been working on...

@jrfnl @urkle ## 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 may resolve it...

Hi @jrfnl. You're so right. I forgot about the [(Close) Parallel Build Webhook](https://docs.coveralls.io/parallel-build-webhook) being a special feature in some integrations, not requiring you to build up that request. So what...

**NOTE**: If you're using a different Coveralls integration and/or are still having trouble determining the correct values for either `build_num` or `repo_token` let me know here, or in the context...