Expand description
Authenticating to the forge as the bot App itself.
GitHub serves the installation-reading endpoints to App credentials
only: GET /repos/{owner}/{repo}/installation takes a JWT signed with
the App’s private key, and no personal access token of any class is
accepted there. So the install-bot step observes as the App: rk
builds the RS256 signing input, signs it in-process with the key bytes
it already holds, and carries the resulting token to the forge through
crate::http, in a header — the JWT is a credential, and
forge-setup:a-secret-never-reaches-argv binds it like any other. No
child process holds the key or the token, so neither can reach an
argument list, an environment, or a stream.
The answers surface only as the classified AppApi and the step
states built from it: no request or response reaches a journal, an
event, or a transcript, and a failure’s reason is scrubbed against the
token before it is returned.
Structs§
- AppCredentials
- The two halves of the App identity. The caller resolves both — the id from the environment, the key from the run’s one read of the named file — so this module never opens anything itself.
Enums§
- AppApi
- One read-only forge answer, asked as the App itself.
Constants§
- REMEDIATION
- What exporting the credentials would enable, named wherever they are absent.
Functions§
- api_get
GET https://api.github.com/{path}with the JWT as a bearer token.- app_id
- The App id from the environment, absent when unset.
- mint
- Mint a short-lived RS256 JWT for the App:
issis the App id,iatsits sixty seconds back against clock drift, andexpnine minutes out, inside the forge’s ten-minute cap.