Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User friendly warning if COVERALLS_REPO_TOKEN is not set #203

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

nidkil
Copy link

@nidkil nidkil commented Dec 14, 2018

Currently when COVERALLS_REPO_TOKEN is not set Coveralls fails with an error message.

Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

For a new user it is not clear what the problem is. There is a warning message, but it is only visible if NODE_COVERALLS_DEBUG is enabled. And even then there is so much debugging information that a user will never see it.

I have added a warning message that is displayed when COVERALLS_REPO_TOKEN is not set. I also added the environment variable COVERALLS_QUIETE to run in quiete mode if required.

@nidkil nidkil changed the title Improve usability User friendly warning if COVERALLS_REPO_TOKEN is not set Dec 14, 2018
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 96.0% when pulling 231270d on nidkil:improve_usability into cc67125 on nickmerwin:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 96.0% when pulling 231270d on nidkil:improve_usability into cc67125 on nickmerwin:master.

@jtwebman
Copy link

jtwebman commented Mar 6, 2022

Since this library doesn't seem to be supported anymore I fix a bunch of things on a fork if you want to check it out and are still pulling the library into your packages: https://github.com/jtwebman/coveralls-next This would be a nice addition!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants