A Git host adapter MUST authenticate through a Git credential helper, through the host's own command-line tool (gh, glab) or through a token read from the environment it is handed, and MUST NOT write a credential into any file, a remote URL, a result or an error; a token MUST be sent only to the host the client serves, and in a header alone.
Enforced (check): .github: cd commons/githost && bun test suite/ — githost-adapters.test.ts, githost-live.test.ts, githost-remote.test.ts: a private repository asked with no credential is not found and typed; the token is read from the environment given to clientFor, sent in a header to the one host it serves, and held in no result, URL or error
Proved by: githost/suite/githost-adapters.test.ts, githost/suite/githost-live.test.ts, githost/suite/githost-remote.test.ts
Written in: githost/src/http.ts, githost/src/mod.ts
Tests: passed: suite/githost-adapters.test.ts plain Git: a remote that wants a credential is unauthorized, never a prompt, and the progr; passed: suite/githost-adapters.test.ts GitHub: a private repository asked with no credential is not-found, as GitHub says, and ev; passed: suite/githost-adapters.test.ts GitLab: a private project asked with no credential is not-found, as GitLab says, and every; passed: suite/githost-live.test.ts GitHub over the live transport: public and private repositories, the credential only in a ; passed: suite/githost-live.test.ts GitLab over the live transport: the credential in `PRIVATE-TOKEN` or `JOB-TOKEN`, never in and 2 more
Cited by: github, Githost, Intellectual Frontiers Capabilities Configuration Management