IW-670: Offline Forgejo issue --json error cases in BATS #737
No reviewers
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli!737
Loading…
Reference in a new issue
No description provided.
Delete branch "IW-670"
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?
Summary
test/forgejo-issue.batsran the Forgejoissue --jsonpath only in live cases that skip withoutFORGEJO_API_TOKEN, so CI never ran it end to end. This PR adds two offline cases that run in CI.Changes
test/forgejo-issue.bats: two offline cases foriw issue 1 --jsonon a Forgejo tracker:FORGEJO_API_TOKEN→ exit 1, empty stdout, stderr namesFORGEJO_API_TOKENbaseUrl(dummy token, no network call) → exit 1, empty stdout, stderr namesbaseUrlwrite_live_forgejo_configis nowwrite_forgejo_config, with ano-base-urloption. The live cases use it too.IssueHarnessTestalready covers the logic at unit level.Testing
project-management/issues/IW-670/implementation-log.md.project-management/issues/IW-670/review-packet.mdRelease notes
See
project-management/issues/IW-670/release-notes.md(Czech). Test-only change; no user-visible behaviour change.🤖 Generated with Claude Code
Closes #670
Issue: IW-670 Phase: 1 - Offline Forgejo issue --json error cases This commit marks the checkpoint for phase 1 context generation. Use wf-implement IW-670 to return to this point. 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Offline Forgejo issue --json error cases Artifacts: - phase-01-tasks.md 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>