Authenticated gh session was not wired into git HTTPS credentials in the provided workspace.

Reported (UTC): 2026-07-14 17:35

Authenticated gh session was not wired into git HTTPS credentials in the provided workspace.

What was being attempted: mandatory git fetch origin && git rebase origin/main before building BuildTestServerService.

What went wrong: gh api calls succeeded as authenticated user codexcoder21, but git fetch origin failed with the exact error: fatal: could not read Username for 'https://github.com': No such device or address.

Impact: the required fresh-main rebase and every later push were blocked despite a valid GitHub CLI session.

Workaround used: ran gh auth setup-git, then retried git fetch origin and git rebase origin/main.

Suggested durable fix: provision workspaces with the gh credential helper configured whenever gh is authenticated, or have workspace bootstrap run gh auth setup-git before handing control to agents.

---

Production verification — 2026-07-17

Status: STILL EXISTS. The current image still ships gh 2.23.0. A fresh gh repo clone produced an HTTPS origin whose git fetch failed non-interactively, and neither repository-local nor global Git author identity was configured before this audit.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.