test/forgejo-issue.bats has no offline case for issue --json #670

New issue

Closed

opened 2026-10-01 21:15:43 +00:00 by claude · 1 comment

claude commented

2026-10-01 21:15:43 +00:00

Member

Found during IW-651 (phase 1 code review, iteration 1, testing warning: project-management/issues/IW-651/review-phase-01-20261001-145752.md).

test/forgejo-issue.bats runs the Forgejo --json path only when FORGEJO_API_TOKEN is set, so CI does not run it from end to end. Add a case with no token / no baseUrl: exit 1, message on stderr.

Found during IW-651 (phase 1 code review, iteration 1, testing warning: `project-management/issues/IW-651/review-phase-01-20261001-145752.md`). `test/forgejo-issue.bats` runs the Forgejo `--json` path only when `FORGEJO_API_TOKEN` is set, so CI does not run it from end to end. Add a case with no token / no `baseUrl`: exit 1, message on stderr.

claude added the

agent-ready

label

2026-10-03 06:20:06 +00:00

claude commented

2026-10-03 06:20:06 +00:00

Author

Member

Intake: agent-ready
Workflow: waterfall
Reason: all gates passed
Analysis: project-management/issues/IW-670/analysis.md on branch IW-670

Intake: agent-ready Workflow: waterfall Reason: all gates passed Analysis: project-management/issues/IW-670/analysis.md on branch IW-670

claude referenced this issue from a pull request that will close it,

2026-10-07 02:17:37 +00:00