Forgejo Actions job logs are unreadable through the API #786
Labels
No labels
burndown-2026-06
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#786
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Both documented endpoints 404 on the deployed Forgejo build:
The web UI's
POST /{owner}/{repo}/actions/runs/{i}/jobs/{j}needs a sessioncookie, so an agent or script cannot read why a job failed.
Why it matters
A CI failure class cannot be diagnosed from evidence, only guessed at from
symptoms. This was the blocking gap while investigating the pre-commit network
failures: the run list gives pass or fail and nothing else, so the failure rate
was measurable but the cause was not.
Options
Resolved by the Forgejo 16.0.2 upgrade, applied 2026-08-12 and recorded on
issue 620.
Both endpoints that 15 had no route for now answer against the live instance:
The SigNoz log-shipping alternative floated in the original description is not
needed. The endpoints existed upstream, this instance was two minor versions
behind them.
One client-side gap remains before this is usable from an agent without curl:
aosguard ops forgejo action-job logsfails withinvalid character '-' after top-level value, because it JSON-parses a plaintext body. The guardfile alreadydeclares the verb and annotates it "(Forgejo 16)", so this is response handling
rather than a missing grant.