Your first run

The check run

Once the trial has started, the next push produces a check run for each job, named <workflow name> / <job name>. A job that calls a reusable workflow produces one check run for each job it calls, named <workflow name> / <calling job> / <called job>, each with its own steps and result — a called job that is skipped shows as skipped. GitHub names its own after the job alone (<calling job> / <called job> for a called one), so re-select any required status check. (Installing the App is not the last of the six steps — nothing runs until the trial is started on your Account.)

A job's ::notice, ::warning and ::error messages become annotations on the check run, as they do on GitHub: at the file and line the command names, or, when it names none, at the line in that step's log, with the title it gives. A failed step adds one of its own, Process completed with exit code N. Up to ten of each level are kept per step, and fifty per job. The check run lists each step with its result and duration, and each annotation with the step it came from; the full log is on the run's page in the Apex dashboard.

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

apex reproduce <run> --job <key> prints the command that runs a past job on your machine, with every secret named and never included. It is not yet available to customer accounts. The apex CLI itself installs with npm install -g @apex-actions/cli.