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
Fail action if there's unformatted files
We need to fail the action in addition to creating a failed check
because the latter for some reason doesn't fail the CI run.
Also set status of check to "action_required" instead of "success" if
all files are formatted but there's build warnings.
Gracefully handle more than 50 warnings
The GitHub annotations API limits us to 50 warnings. We now handle this
gracefully (instead of throwing an error) by informing the user of the
limit.
Don't require builds to be listed manually
We assume that all build artifacts created so far are build logs, and
simply download them all for analysis. Also update all package
dependencies.
Switch to GitHub Checks API, + more
Results are now reported via the GitHub Checks API, instead of creating
commit comments. This reduces overall noise and integrates nicely with
the GitHub UI. Additionally, per-file warnings and errors are now also
added as file annotations.
This also changes the expected build log naming to support unique build
names (which prevents them from clashing during concurrent workflow
runs). Build log names are now expected to be of the form
"build-${name}-${run_id}-${run_number}-log".
Finally, this updates all package dependencies to their newest version.
Report results as commit comments
This allows us to run this job on both PRs as well as plain commits in
arbitrary branches. GitHub displays commit comments inside the PR
conversation tab, so the previous behavior is still maintained.