Make PR, issue, release, and CI mutation failures actionable #636

Closed
opened 2026-05-06 19:55:42 +00:00 by barrettruth · 0 comments
Owner

Parent: #634

Problem

Mutation actions route through lua/forge/action/ops.lua and often fall back to generic messages such as merge failed, close failed, delete failed, cancel failed, or rerun failed. In the merge case, this can hide the actual CLI reason while the PR remains open.

Scope

  • Improve run_forge_cmd / run_forge_task failure handling.
  • Include useful backend CLI output for PR merge, PR close/reopen/approve/draft, issue close/reopen, release delete, and CI cancel/rerun.
  • Thread failure details to callbacks where picker refresh/revert behavior depends on the failure.
  • Add tests for a failed merge that includes stderr and a failed command with blank streams.

Non-goals

  • Do not change optimistic success behavior.
  • Do not implement new backend actions.
Parent: #634 ## Problem Mutation actions route through `lua/forge/action/ops.lua` and often fall back to generic messages such as `merge failed`, `close failed`, `delete failed`, `cancel failed`, or `rerun failed`. In the merge case, this can hide the actual CLI reason while the PR remains open. ## Scope - Improve `run_forge_cmd` / `run_forge_task` failure handling. - Include useful backend CLI output for PR merge, PR close/reopen/approve/draft, issue close/reopen, release delete, and CI cancel/rerun. - Thread failure details to callbacks where picker refresh/revert behavior depends on the failure. - Add tests for a failed merge that includes stderr and a failed command with blank streams. ## Non-goals - Do not change optimistic success behavior. - Do not implement new backend actions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
barrettruth/forge.nvim#636
No description provided.