Trace a deployment back to its GitHub Actions jobs
On the environment’s Deploys tab, open a workflow deployment to see which GitHub jobs counted together and when its verification started.
Identify the landing event and the jobs it includes#
GitHub Actions jobs count as one deploy when they belong to the same workflow run and deploy the same commit to the same GitHub Environment for the same deployment task. They share one set of four checks. Re-running a job that already deployed, as when you re-run the last good run to roll back, starts a new deploy with its own four checks, and the deploy it re-ran keeps its own. Re-running a job that failed stays in the same deploy. A deployment created outside GitHub Actions counts as a deploy of its own. Older deployments that Proofline already verified separately keep their original checks.
The deploy lands when its last job succeeds. Proofline starts the checks after eight minutes pass without another job landing. If a job or the workflow is still running, Proofline keeps waiting for up to two hours from when it first saw work still running. The checks use the time of the last success.
Select a deploy's row to see its checks and signal readings. For a deploy with several GitHub deployments, Jobs lists them in the expanded row and on the deploy's page. An administrator also sees each gap of the deploy that a setup step closes, beside that step, while the Inbox lists that setup task. Select Open at the end of the row to go to the deploy's page. Show more deploys below the list loads 25 more at a time.