Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| A mirror of a GitHub repository whose workflows g1t runs, in CI failover, during a takeover or with CI kept warm, now shows their results on GitHub: each status g1t sets on a commit, a workflow run's or a deploy's, goes to the commit there through g1t's GitHub App as a commit status named under g1t / (g1t / CI / push; g1t / deploy stays as it is), with its state, its description and a link back to g1t, once each time it changes, and commits made on g1t during a takeover are skipped. It is on by default and turned off with Report checks to GitHub in the mirror's settings, or report_checks through the API. The app needs the Commit statuses permission; until an installation has it, the mirror's settings say g1t can't report checks to GitHub and why, and the line goes once a status gets through. Statuses set by workflow runs, deploys and g1t's other parts are now published as status.created, as ones set through the API were, so webhooks hear them too. The mirroring, actions, GitHub, checks, webhooks and self-hosting guides say so. | 1 | -- Reporting checks to a mirror's remote (src/remotes.rs, on_status). |
| 2 | -- checks_error: why g1t could not report the last check to it, such as | |
| 3 | -- the GitHub App lacking the Commit statuses permission; cleared once a | |
| 4 | -- report goes through. Kept apart from last_error, which every sync | |
| 5 | -- clears. | |
| 6 | ALTER TABLE remotes ADD COLUMN checks_error TEXT; |