GitHub Community
-
Select Topic AreaBug BodyConsider this run: https://github.com/jsoref/annotation-limits/actions/runs/5655942044 10 errors, 10 warnings, and 10 noticesAnnotations Fwiw, there's a per step per severity annotation limit of 10 (this is documented somewhere), and there's a per job limit of 50 total annotations (also documented somewhere). I can't think of any good reason to sort I put together a more random list because I wanted to understand a bit more about ordering: https://github.com/jsoref/annotation-limits/actions/runs/5656281688 16 errors, 17 warnings, and 17 noticesAnnotations left It is not simply taking the first n items, nor is it sorting them by their outputs (beyond the fact that it's sorting items based on their severity, alphabetically!). Anyway, bottom line: Please do not sort severities alphabetically. Severities should be sorted by severity. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
We snuck this ship in yesterday as part of adding a job level view of annotations :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, here's a new run (the first run attempt crashed, which is fun):
log 1log 2log 3log 4log 5
I'll not sure I can explain which log entries were taken... I think it's most of log 2 and 1 from log 4? |
Beta Was this translation helpful? Give feedback.
We snuck this ship in yesterday as part of adding a job level view of annotations :)