-
Notifications
You must be signed in to change notification settings - Fork 63
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
v2.7.1 stopped sending coverage comments. #235
Comments
I experienced this as well: https://github.com/apollo-elements/apollo-elements/runs/1189033952?check_suite_focus=true 0 seconds, no console output |
@bennypowers Would you mind turning on debug mode and sharing the results here? You can set the |
@dashmug The attached screenshot shows the codeclimate bot, which has nothing to do with this action. Can you help me understand how that is relevant here? |
@paambaati It is relevant because it means CodeClimate did not receive any coverage data so the bot isn't triggered to do anything. |
@dashmug @bennypowers I was able to figure out the issue and I've now pushed a new release - please try |
@paambaati v2.7.2 fixed it. Thank you very much. |
Thanks for the update
- name: Test
run: yarn test
- name: Test & Publish Code Coverage
uses: paambaati/[email protected]
env:
CC_TEST_REPORTER_ID: ${{ secrets.CC_TEST_REPORTER_ID }} perhaps the default command should be removed? |
@bennypowers The default command needs to be set to an empty string in — Line 11 in 4a8e577
I'd appreciate it if you can send a PR. In the meantime, please specify a coverage command explicitly. |
יאללה PR incoming |
Describe the bug
CodeClimate coverage comments stopped updating after upgrading. I believe there were some failures in sending the coverage data to CodeClimate.
I'm referring to this:
Version v2.6.0 works without problems. I have reverted back to it in the mean time.
Version of
codeclimate-action
you're usingv2.7.1
Example links
I'll post some screenshots when I get the time.
Expected behavior
It will continue behaving as it was before.
Additional context
TODO
The text was updated successfully, but these errors were encountered: