James Kessler

Ok, @dmarin, I'll reply here if I think this is affecting Gitlab generally.

Also, @dmarin — I replied to your email request.

General update: It looks like in both cases here there was an issue with the user's Gitlab API token. Normally, those would not expire, but in one of the cases...

Update: Looks like this is a breaking change in Gitlab 15.0: [GitLab.com is moving to 15.0 with a few breaking changes](https://about.gitlab.com/blog/2022/04/18/gitlab-releases-15-breaking-changes/#oauth-tokens-without-an-expiration) > GitLab no longer supports OAuth tokens [without an...

Hi, @dmarin. not at this time, sorry to say. I have pinged the card, which will get it a look, and I'll follow up with our developers on Mon. If...

@dkfellows Thanks for the clear description of your goal and your use case. Unfortunately, Coveralls isn't currently set up to handle monorepos or multi-repo projects (submodules or not) and, right...

@avtikhon (Cc: @caleb15, @szechyjs), thanks. Reproduced and reported. Will post updates here.

Hi @Montana. When you say you have: > made the personal_repo as an environment variable What do you mean by "personal_repo"? I ask because POSTing coverage to the [https://coveralls.io/api/v1/jobs endpoint](https://docs.coveralls.io/api-reference)...

Hi, @Montana. Just following up to see if you got this resolved.

Hi @davidhewitt. I can't tell from the [article you cite](https://blog.rust-lang.org/inside-rust/2020/11/12/source-based-code-coverage.html) what the full spec of that mode's coverage report format would be, but I can tell you that coveralls supports...