Your first run

The check run

The first push after the App is installed produces a check run on the commit, named after the job exactly as GitHub would name it. Annotations from ::error and ::warning commands appear inline on the diff. The log is one click away.

The verdict

Open the run. At the top is a verdict for every workflow file in the repository — including the ones that ran nothing, and which filter said no. If a workflow you expected did not run, this is where the reason is.

Step timing

Each step in the job shows its duration and, after a few runs, how it compares with its own history for that workflow and matrix leg. Steps that are slower than usual are marked.

Flaky tests

If a job writes JUnit, TAP or CTRF reports, Apex discovers them in the workspace without any change to the workflow. A test that passed and failed at the same commit is a flake; it is named on the pull request as a warning and never turns a green run red.

Reproducing a failure

A failed job shows the exact command to run it on your machine:

Every secret the job used is named in the output and never included. Set the values in your shell and run the command.