James Kessler

Two (2) related issues here: 1. https://github.com/nickmerwin/node-coveralls/issues/80 2. https://github.com/nickmerwin/node-coveralls/issues/280 (2) indicates an upgrade (or downgrade) might resolve. Have suggested and asked the user their current version.

hi @irverysmart and @lc-soft. for future reference, the more active resource for coveralls user support is here: https://github.com/lemurheavy/coveralls-public/issues that error usually indicates a missing or incorrect repo token for your...

@dinko-pehar the answer is yes, only LCOV. That’s for the Coveralls GitHub action on its own. It only accepts LCOV. That said, some other integrations—language specific, community-created integrations—support other coverage...

@dinko-pehar in that case check out Coveralls’ new Universal Coverage Reporter: https://github.com/coverallsapp/coverage-reporter It’s written in Crystal and currently has support for LCOV and SimpleCov. Maybe you can contribute a plug-in...

Potentially related to: https://github.com/lemurheavy/coveralls-public/issues/1530

Hi @ankitm123. Thanks for this. Did you say these changes support PR builds only? Or both "pull_request" and "push" builds? A full coveralls integration would cover both builds, since "push"...

> Is there something wrong with this pull request? @blaskovicz apologies. We ran an auto-archiving bot on our issues and this PR got swept up in them. No issue with...

@daurnimator this would not be fixed for old builds, but given the age and nature of the issue I would suspect it's been long fixed, otherwise we'd hear about similar...

Hi @theogf. I'll need the Coveralls Repo URL (or project name) to help you with this. I tried to guess, but it looks like you're running a number of projects...

@theogf thanks! I'll reply there. @dmarin are you also on Gitlab?