The agent's GitHub switch, settings and what may be turned on

enabled is the switch that applies at once (PUT …/github/enabled). github is the agent's own GitHub settings, or the active release's pin while the agent has none; null when neither exists, when legacy_defaults is what a first save starts from (no repository, push approval off, nothing optional; the release itself keeps asking a person before each push until settings are saved). settings_revision is the row's revision (null without a row) and start_repository_id a repository kept for compatibility: once the agent has a settings row, a session naming none starts without a repository whatever this holds, and attaches what the task needs. push_attached (allow, ask or deny) says whether a push to a repository the session attached needs a person: the row's value, ask for a row saved before the field existed, and allow while there is no row (what a first save writes). Settings are saved with PUT …/github/settings, never as a release. options.repositories lists the catalog's GitHub repositories with why one cannot be picked (repository_not_allowed by the workspace's repository ceiling; repository_ceiling_unset is true while the workspace has none yet, and the list is then judged against the default the first save writes, without writing it on this read), and installed: whether the author and the reviewer App are installed on each, as GitHub answers now (null when there is no such App or no answer). options.features says, per optional permission, why it cannot be turned on: github_host_unsupported (every chosen repository is on a GitHub Enterprise host), over_workspace_ceiling, no_reviewer_app, or app_permission_missing (the App's permissions as last read lack it; the token request decides). Whoever manages the agent reads it, and so do the live members of its managing team.

Auth: cookie session only; no scope.