Closed dancrumb closed 2 months ago
We're hitting the same issue. I assume this only happens with markdown-report-on-step-summary: true
(we have a lot of warnings 😞)
I'm experiencing the same unfortunately, does anybody know of a workaround that does not involve suppressing the warnings? Because on a large monorepo with microservices, we've got something like:
Only 65535 characters are allowed; 320944 were supplied.
which is waaaay above the limit
This seems like a character limit on the check run summary.
does anybody know of a workaround that does not involve suppressing the warnings
I don't know if there is a good answer without simplifying the summary to include the number of errors and warnings without actually listing them all out.
This seems like a character limit on the check run summary.
does anybody know of a workaround that does not involve suppressing the warnings
I don't know if there is a good answer without simplifying the summary to include the number of errors and warnings without actually listing them all out.
I'd support the idea of a such minimal summary and we can look into other ways of obtaining a complete list
I am working on v3
(in progress) and will make it so when only-pr-files
is true
only those files are included in the summary. Please let me know if any of you are interested in helping to test that version.
edit: to test please update your action reference to uses: ataylorme/eslint-annotate-action@v3-beta
3.0.0
has been released. Please update any references to the v3
branch instead of v3-beta
. Make sure to read the Changelog as there are breaking changes (GH_TOKEN input has changed)
This looks like a regression of #32
My config is:
The logs look fine until: