Deployments

Deployments read workflow runs. The browser does not hold the token.

4 repos

Failed
example-org/example-app

deploy.yml on main

Latest
deploy.yml on main failed
Token
env GITHUB_TOKEN
Pull request runs are ignored for the release result.
Failed
example-org/infra

deploy.yml on main

Latest
deploy.yml on main failed
Token
env GITHUB_TOKEN
Pull request runs are ignored for the release result.
Running
example-org/docs-site

deploy.yml on main

Latest
deploy.yml on main is running
Token
env GITHUB_TOKEN
Pull request runs are ignored for the release result.
Not tracked
example-org/status-page

workflow on main

Latest
No workflow is configured
Token
env GITHUB_TOKEN
Pull request runs are ignored for the release result.
Sample data · not live · Oct 20, 4:41 PM CDT

Workspace

Find anything

How status works

Every badge is an observation with a time. Fresh, stale, unknown, and failed stay distinct. A missing report is never shown as healthy.

The browser never receives tokens, SSH keys, or heartbeat secrets. Those stay in environment variables and in the status Action.