phase-merge run again after its own merge answers a bare 405, because it has no already-merged path #579

New issue

Open

opened 2026-09-20 10:29:03 +00:00 by claude · 3 comments

claude commented

2026-09-20 10:29:03 +00:00

Member

phase-merge re-run after its own successful merge answers a bare Error: Forgejo API error: 405 from mergeWithDelete, because it has no already-merged path. The forge state is the fact; a merged pull request should skip the merge and go straight to the advance, so the command is re-enterable after the advance fails.

Found while working IW-555. Companion to the advance failure filed as #578.

`phase-merge` re-run after its own successful merge answers a bare `Error: Forgejo API error: 405` from `mergeWithDelete`, because it has no already-merged path. The forge state is the fact; a merged pull request should skip the merge and go straight to the advance, so the command is re-enterable after the advance fails. Found while working IW-555. Companion to the advance failure filed as #578.

mph referenced this issue from a commit

2026-09-20 20:24:03 +00:00

workflow: Triage lessons for IW-555

claude commented

2026-10-15 19:24:23 +00:00

Author

Member

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

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

claude added the

agent-ready

label

2026-10-15 19:24:23 +00:00

claude commented

2026-10-15 20:56:44 +00:00

Author

Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon iw plugin does not compile against iw-cli main, so no phase ran

iw-cli main changed fetchPullRequestForBranch on the command env to return Either[TrackerError, …] (#778). The kanon plugin's lib/batch/ForgeCatchUp.scala still expects Either[String, …]. The compile fails before batch-implement writes its log, so the lines below come from its console output. This blocks batch-implement for every iw-cli issue until the plugin is updated. The issue itself needs no change.


[error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7
[error] Found:    Either[iw.core.model.TrackerError, Option[batch.ForgeState]]
[error] Required: Either[String, Option[batch.ForgeState]]
Compilation failed

Implement: needs-human Reason: batch-implement exit 1 — the kanon iw plugin does not compile against iw-cli main, so no phase ran iw-cli main changed `fetchPullRequestForBranch` on the command env to return `Either[TrackerError, …]` (#778). The kanon plugin's `lib/batch/ForgeCatchUp.scala` still expects `Either[String, …]`. The compile fails before `batch-implement` writes its log, so the lines below come from its console output. This blocks `batch-implement` for every iw-cli issue until the plugin is updated. The issue itself needs no change. ``` [error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7 [error] Found: Either[iw.core.model.TrackerError, Option[batch.ForgeState]] [error] Required: Either[String, Option[batch.ForgeState]] Compilation failed ```

claude added

needs-human

and removed

agent-ready

labels

2026-10-15 20:56:44 +00:00

claude commented

2026-10-16 17:10:36 +00:00

Author

Member

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.

claude added

agent-ready

and removed

needs-human

labels

2026-10-16 17:10:36 +00:00