v8

• Fail action if there are no build log artifacts
• Fix check not showing up for runs triggered by pull_request event
• Update all dependencies

v7: 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.

Also take unformatted files into consideration for annotations limit

v6

Also take unformatted files into consideration for annotations limit

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.

v2: 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.

v1

Initial commit