Administer Forge¶
This page describes the administrator's role around the reduced Forge surface: the account boundary, repository authorization and review. It adds no command; the supported customer commands are in CLI reference.
Administrators may have to approve the Forge GitHub App installation on the ownership that holds the repository, and the App must then be associated with the profile, agent and repository that deploy it. This portal does not document an administrative command surface.
See Connect GitHub for the four checks and the one next action for each state.
Administrative responsibilities¶
| Responsibility | Boundary |
|---|---|
| Account setup | Provide the local context required by the approved Aegis distribution. |
| Repository authorization | Approve Forge App access when a deployment requires repository access. |
| Source control | Leave ordinary Git operations under the operator's GitHub authority. |
| App identity | Let authorization and repository context derive the identity. |
| Runtime contract | Review the committed manifest and local HTTP behavior. |
Review packet¶
Keep the repository origin, commit, manifest diff, local HTTP result, and deployment result. Exclude credentials and other secret values.
Prohibited configuration¶
Do not require environment, tenant, account, installation, or app identity selectors. Do not inject a repository workflow.
Read Connect GitHub, Deploy, and Security and trust.