Juliette

@afinetooth Please feel free, but I have seen the same issue with multiple PRs now, so it definitely isn't a one-off. Some other examples: * https://github.com/PHPCSStandards/PHPCSUtils/pull/304 - Introduced a new...

Well, yes, one of the builds referenced above switched a PHP version (PHP 7.4 to 8.1), but it didn't change the order of the jobs, it was just a straight...

> So, does that mean you're mixing two integrations?: > > * using [php-coveralls](https://github.com/php-coveralls/php-coveralls) to send your jobs, > * then using the [Coveralls Github Action](https://github.com/marketplace/actions/coveralls-github-action) to close your build?...

@afinetooth Hi James, thanks for getting back to us. I'll implement this tomorrow in a few repos for which I expect a fair number of builds over the next few...

Looking your instructions over again - I actually have another question: > But substitute your `repo_token`, and your `build_num` (the same value you used for `build_num` in your [(Close) Parallel...

Thanks for gettting back to me @afinetooth ! > That value will be different for different CI service / integration combinations, but for the [Coveralls Github Action](https://github.com/marketplace/actions/coveralls-github-action), the correct environment...

@OndraM Good question, though in that case, I wonder if that should be changed in more places (and in the documentation in various places too...) See this workflow example: https://github.com/lemurheavy/coveralls-public/issues/1631#issuecomment-1251649121

> 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 "secrets" (Settings ->...

Agreed, I was just answering your question on the "how", not advocating for making this change, which would mean a lot of work for every single user of Coveralls.

> 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 Any news ?