-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Generating report failed with TypeError: Cannot convert undefined or null to object #388
Comments
Hello @QuentinLemCode 👋, Looks like the coverage file |
@ArtiomTr Thanks for reply |
Try to specify: with:
coverage-file: ./coverage/report.json
base-coverage-file: ./coverage/report.json # this line added
github-token: ${{ secrets.GITHUB_TOKEN }}
threshold: 90
annotations: coverage
skip-step: all This will skip coverage comparison. This is not ideal, but at least your CI will work for now. I need more time to dig deeper into this issue |
Did you find time to look deeper into this yet? Just now, I could observe the same behavior: jobs:
coverage:
runs-on: ubuntu-latest
permissions:
checks: write
pull-requests: write
contents: write
steps:
- uses: actions/checkout@v4
- uses: ArtiomTr/[email protected]
with:
package-manager: yarn
output: comment, report-markdown
icons: emoji
threshold: 80 The code above runs perfectly fine on PRs but breaks on
Could the reason for this behavior be that there is no PR context on |
really want to use this but no matter what combination of configs I use i always get the "Error: TypeError: Cannot convert undefined or null to object" as outlined in this issue. |
Hi there, Today I got the same issue and it seems to be related with the "threshold" flag.
|
Describe a bug
Hello,
The action fail on main branches while it works on PR.
See the screenshot below and the report.json gist link
Expected behavior
The report is generated and a comment is added to the PR
Details
action.yml file
Screenshots
https://gist.github.com/QuentinLemCode/3600641d8b3db7c6c5753c1896ce9224
Additional context
The text was updated successfully, but these errors were encountered: