feat(ci): support rerunning CI runs from Forge #270

New issue

Closed

opened 2026-04-15 02:40:35 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-04-15 02:40:35 +00:00

CI rerun support looks useful, but it should stay scoped and explicit rather than turning into a generic passthrough-args feature.

What we discussed:

treat rerun as a first-class Forge CI action, not arbitrary CLI flag forwarding
prefer picker-driven CI rerun first, then consider :Forge ci rerun {run-id} later if it still feels right
support it only on backends that expose a clean rerun/retry surface

Backend notes:

GitHub CLI supports rerunning a run (gh run rerun <run-id>) and can also target failed jobs or a specific job
GitLab CLI exposes retry at the CI job level (glab ci retry <job-id>)
Codeberg/tea does not appear to expose a comparable rerun action right now

Open design questions:

should v1 rerun only selected repo CI runs, or also nested PR checks?
should rerun require confirmation in the picker?
what should the picker action/key be?
should command-surface support be added at all, or should this stay picker-only?

Non-goal:

do not add a generic "forward arbitrary args to the underlying forge CLI" escape hatch

CI rerun support looks useful, but it should stay scoped and explicit rather than turning into a generic passthrough-args feature. What we discussed: - treat rerun as a first-class Forge CI action, not arbitrary CLI flag forwarding - prefer picker-driven CI rerun first, then consider `:Forge ci rerun {run-id}` later if it still feels right - support it only on backends that expose a clean rerun/retry surface Backend notes: - GitHub CLI supports rerunning a run (`gh run rerun <run-id>`) and can also target failed jobs or a specific job - GitLab CLI exposes retry at the CI job level (`glab ci retry <job-id>`) - Codeberg/tea does not appear to expose a comparable rerun action right now Open design questions: - should v1 rerun only selected repo CI runs, or also nested PR checks? - should rerun require confirmation in the picker? - what should the picker action/key be? - should command-surface support be added at all, or should this stay picker-only? Non-goal: - do not add a generic "forward arbitrary args to the underlying forge CLI" escape hatch

barrettruth commented

2026-04-17 16:35:01 +00:00

likely only a feature once a pr "view" and fugitive/octo-like notion is begun