GitHub Community
Annotation limitation #26680
-
|
I am trying to create a linting tool which runs as a GitHub action, however I keep running into limitations on GitHub actions. So it looks like only 10 annotations are shown, but when my linting tool on a codebase, there could be like 500 errors, so this is obviously not ideal. It seems like with a GitHub App you are allowed to add infinite amount of annotations, which sounds perfect, however than I have to migrate to a GitHub App, which is annoying as I want to run it with GitHub actions. I also tried creating a review instead, however reviews can only add comments to lines which are changed in the PR and you cannot add a review if the changes are not in a PR. Also the review API crashes/times out if you add around 20 comments in one request. I am kinda in a loss, what other solutions have I forgotten to look into? Or did I oversee something? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
|
Currently, GitHub Actions does not support so much annotations in a workflow run, the below is a summary of the limitation:
There is a similar ticket as reference: https://github.community/t5/GitHub-Actions/Maximum-number-of-annotations-that-can-be-created-using-GitHub/m-p/39085/highlight/false#M3660 |
Beta Was this translation helpful? Give feedback.
-
|
Yep and that limitation is why I cannot show the errors as annotations, as 10 annotations is a really low limit. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, currenly we have no any available way to bypass the limitation. If your projects really need more annotations, I recommend you directly report a feature request here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions. |
Beta Was this translation helpful? Give feedback.
-
|
I've done so here: https://github.com/orgs/community/discussions/68471. Was very frustrated to run into this. |
Beta Was this translation helpful? Give feedback.
-
|
It’s possible to output Markdown summaries now, which can be used to generate nicely formatted reports:
 Supercharging GitHub Actions with Job Summaries | The GitHub BlogYou can now output and group custom Markdown content on the Actions run summary page. Est. reading time: 3 minutes |
Beta Was this translation helpful? Give feedback.
-
|
@olivernybroe have file a feature request? If yes could you link it here? |
Beta Was this translation helpful? Give feedback.
@olivernybroe ,
Yeah, currenly we have no any available way to bypass the limitation.
If your projects really need more annotations, I recommend you directly report a feature request here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.