Expose Forgejo CI cancel through documented tea command #630

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

Problem

Forgejo CI cancel was removed after live smoke testing showed this self-hosted Forgejo instance returning 405/404 behavior. However, tea documents tea actions runs delete|remove|rm|cancel as the supported workflow-run delete/cancel surface.

That means Forge should expose cancel for Forgejo through the documented tea CLI command even if one particular instance rejects the operation. Rerun should remain hidden unless there is a documented tea rerun command.

Scope

  • Restore Forgejo cancel_run_cmd through the documented tea workflow-run command.
  • Keep Forgejo rerun_run_cmd absent.
  • Update :h forge-compatibility so cancel and rerun are tracked separately.
  • Update the backend-capabilities tracker to reflect the same split.
  • Add focused tests for the Forgejo command and cancel-only picker affordance.

Non-goals

  • Do not add Forgejo rerun without documented tea support.
  • Do not special-case this self-hosted instance failing the documented cancel command.
## Problem Forgejo CI cancel was removed after live smoke testing showed this self-hosted Forgejo instance returning 405/404 behavior. However, tea documents `tea actions runs delete|remove|rm|cancel` as the supported workflow-run delete/cancel surface. That means Forge should expose cancel for Forgejo through the documented tea CLI command even if one particular instance rejects the operation. Rerun should remain hidden unless there is a documented tea rerun command. ## Scope - Restore Forgejo `cancel_run_cmd` through the documented tea workflow-run command. - Keep Forgejo `rerun_run_cmd` absent. - Update `:h forge-compatibility` so cancel and rerun are tracked separately. - Update the backend-capabilities tracker to reflect the same split. - Add focused tests for the Forgejo command and cancel-only picker affordance. ## Non-goals - Do not add Forgejo rerun without documented tea support. - Do not special-case this self-hosted instance failing the documented cancel command.
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#630
No description provided.