-
Notifications
You must be signed in to change notification settings - Fork 256
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
[SUPPORT REQUEST] Add support for generic Github Actions implementation #317
Comments
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 I use this version in that library in a very generic way (https://github.com/jtwebman/coveralls-next/blob/master/.github/workflows/test.yml) but I used a different service name to do it as I couldn't figure out their logic for using the tool directly and using the GitHub token instead. |
Via support request, the feature request is to add support for a "Vanilla" implementation of Github Actions, fo users who for one reason or another cannot use the Coveralls Github Action.
The goal would be to add support for Github Actions CI that would not require the Coveralls Github Action, which means populating all JSON params for a user on node-coveralls that is using Github Actions alone. This entails mapping values from the environment like
service_job_id
.To distinguish from the Coveralls Github Action, we could also add a usage note to use
github
forservice_name
, which would distinguish "vanilla" implementations from Coveralls Github Action ones.The text was updated successfully, but these errors were encountered: