iterative-works/iw-cli
Watch
3
0
Fork
You've already forked iw-cli
 0
Code Issues 119 Pull requests 1 Projects Releases 34 Packages Wiki Activity Actions

Phase 1: Extract ForgejoIssueTimeline + move its tests #729

Merged
claude merged 12 commits from IW-671-phase-01 into IW-671 2026-10-07 00:36:25 +00:00
Conversation 0 Commits 12 Files changed 13 +603 -362
claude commented 2026-10-06 23:53:17 +00:00
Member
Copy link

Phase 01 implementation for IW-671.

Files

Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-671-phase-01/

Phase 01 implementation for IW-671. ### Files Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-671-phase-01/
- Move the timeline cluster from ForgejoClient into ForgejoIssueTimeline, with read taking the page GET as a parameter
- Make TextResponse a top-level private[adapters] type; fetchIssueState calls ForgejoIssueTimeline.read
- Move the timeline unit tests to ForgejoIssueTimelineTest and add four direct timelineComplete tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolved:
- analysis.md: How does the phase 1 branch get past the pre-push hook without WEBAWESOME_NPM_TOKEN? → the next run has the token in its environment; run ./iw phase-pr again, no bypass

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019J4fPYHbmD9dNPDheSrUGd
docs(IW-671): follow-up on pre-push hook outliving the SSH push connection
Some checks failed
CI / changes (pull_request) Successful in 5s
Details
CI / contract (pull_request) Has been skipped
Details
CI / format (pull_request) Successful in 11s
Details
CI / lint (pull_request) Successful in 12s
Details
CI / compile (pull_request) Successful in 1m53s
Details
CI / dashboard-build (pull_request) Successful in 1m27s
Details
CI / test (pull_request) Failing after 18m10s
Details
cb2eedc160 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(IW-671): retry the itest server on a bind failure Undertow wraps
All checks were successful
CI / changes (pull_request) Successful in 5s
Details
CI / contract (pull_request) Has been skipped
Details
CI / format (pull_request) Successful in 10s
Details
CI / lint (pull_request) Successful in 14s
Details
CI / compile (pull_request) Successful in 1m37s
Details
CI / dashboard-build (pull_request) Successful in 1m29s
Details
CI / test (pull_request) Successful in 18m18s
Details
0821fc2228 
Undertow reports a taken port as a RuntimeException around the
BindException, so ItestServer failed instead of trying another port.
Read the whole cause chain.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude merged commit a92da1aed6 into IW-671 2026-10-07 00:36:25 +00:00
claude deleted branch IW-671-phase-01 2026-10-07 00:36:26 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
agent-ready

   
bug
Something isn't working

  
contract
Run the tool-contract suite on this PR

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
needs-human

   
needs-input
Intake asked the human a question on the issue; waiting for the answer

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/iw-cli!729
No description provided.