-
Notifications
You must be signed in to change notification settings - Fork 78
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
Upload to coveralls.io only if 'push' on 'HazyResearch/fonduer' #392
Conversation
Please see the step is skipped on a forked repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This PR fails.
@lukehsiao any idea? |
Not sure. The configuration sets the env var, and the secret is in the repo: This might be due to the secret not being passed correctly? |
Oh, it is clearly stated in the image you attached:
|
Or maybe "Coveralls GitHub Action" works better. |
"Coveralls GitHub Action" only supports LCOV file ( For this reason, some people switched from coveralls to codecov. |
Hmmm, I'm fine with switching to codecov, there is no particular reason we are using coveralls. |
I think codecov is easier solution here. |
Let's fix this for now. We can discuss if we should switch to codecov in a different issue/pr. |
Coveralls.io cannot be easily used by GitHub Actions because the secret token is not passed to PRs which are opened by third-party forks (#392). Furthermore, Coveralls.io's GitHub Action only supports LCOV files (coverallsapp/github-action#30). But, coverage.py generates .coverage files. Since they are roughly equivalent in functionality for our purpose, we switch from coveralls.io to CodeCov.
Before doing the switch give that one a try, I've just built a coveralls action that works for pull requests https://github.com/marketplace/actions/coveralls-python |
This will close #391 .