You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think fatal matches should be printed first due to GitHub Actions' limit of 10 warnings and 10 errors (https://github.com/orgs/community/discussions/26680) - generally displaying things that actually impact the build is more useful than showing already known issues, considering anything beyond that cap won't be displayed by GitHub.
Doing this would make progressive mode more useful when using GitHub Actions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently when running GitHub Actions there is no particular ordering to displaying GitHub Action specific output, as can be seen here.
ansible-lint/src/ansiblelint/app.py
Lines 96 to 100 in e248b64
I think fatal matches should be printed first due to GitHub Actions' limit of 10 warnings and 10 errors (https://github.com/orgs/community/discussions/26680) - generally displaying things that actually impact the build is more useful than showing already known issues, considering anything beyond that cap won't be displayed by GitHub.
Doing this would make progressive mode more useful when using GitHub Actions.
Beta Was this translation helpful? Give feedback.
All reactions