-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Update 3.0.0 Release Notes #251
Comments
TheKevJames/coveralls-python#251 modified: .github/workflows/main.yml modified: CHANGES.txt
Isn't the actual issue here that running in Github Actions is no longer properly auto-detected, and not the documentation about the service name being wrong? |
There is a pinned issue here - #252 Sounds like there is no known solution for auto detection at this time. |
Yeah, the big issue is that we can autodetect Github Actions, but we can't autodetect which service name Github Actions needs for this specific run. As far as we can tell at this point, the only option is for users to set the explicit name if their usecase requires a non-default service name. |
v3.0.0 of coveralls-python now requires `--service` be specified for things to work with Github Actions. See [1]. [1] - TheKevJames/coveralls-python#251
v3.0.0 of coveralls-python now requires `--service` be specified for things to work with Github Actions. See [1]. [1] - TheKevJames/coveralls-python#251
v3.0.0 of coveralls-python now requires `--service` be specified for things to work with Github Actions. See [1]. [1] - TheKevJames/coveralls-python#251
Thank you for the great work on this package.
Upon running a build today on GitHub actions, coveralls.io submission failed with a
422 Client Error: Unprocessable Entity
error when submitting to coveralls.io.The release notes look to have a typo (it says to set
service-name
vsservice
) on the command to override the service name.With my GitHub actions build I had to run:
When setting this option, the submission to coveralls started working again.
The text was updated successfully, but these errors were encountered: