commit-docs / commit-changes: check Forgejo CI via the forgejo extension before merging #129

New issue

Closed

opened 2026-08-30 04:16:45 +00:00 by david · 0 comments

david commented

2026-08-30 04:16:45 +00:00

Owner

Both commit-docs and commit-changes currently instruct: "the extension doesn't surface CI — check the web UI; same for fj" — now stale: the forgejo pi extension ships read-only Forgejo Actions tools that CAN surface CI (forgejo_action_runs, forgejo_action_run_view, forgejo_action_jobs, forgejo_action_job_log, forgejo_action_run_logs).

Update both skills with a "Checking CI on Forgejo" how-to:

forgejo_action_runs head_sha=<PR head sha> → run status (primary filter; catches push AND pull_request-event runs, robust for fork PRs). Lighter alternative: ref: refs/heads/<branch> (misses PR-event runs and fork branches).
On failure: forgejo_action_jobs → forgejo_action_job_log (pass refresh: true after a re-run) to report why.
Version/fallback: Actions endpoints require Forgejo v16+. If forgejo_action_runs errors (e.g. 404 — instance predates v16 or Actions disabled) → fall back to the web UI. Non-Actions CI (commit statuses from external CI) is invisible to the extension → web UI.
Caching: logs are cache-first; run metadata is live.

Behavior change (generic merge policy, both skills): all authorised merges wait for green — when merging is authorised and CI is still running, poll forgejo_action_runs up to 15 minutes, then merge on success / stop-and-report on failure, cancelled, or timeout. No runs → "none configured" → merge.

Ships as one PR touching both skills + CHANGELOG.md (Unreleased → Changed).

Both `commit-docs` and `commit-changes` currently instruct: *"the extension doesn't surface CI — check the web UI; same for `fj`"* — now stale: the `forgejo` pi extension ships read-only Forgejo Actions tools that CAN surface CI (`forgejo_action_runs`, `forgejo_action_run_view`, `forgejo_action_jobs`, `forgejo_action_job_log`, `forgejo_action_run_logs`). Update both skills with a "Checking CI on Forgejo" how-to: - `forgejo_action_runs head_sha=<PR head sha>` → run status (primary filter; catches push AND pull_request-event runs, robust for fork PRs). Lighter alternative: `ref: refs/heads/<branch>` (misses PR-event runs and fork branches). - On failure: `forgejo_action_jobs` → `forgejo_action_job_log` (pass `refresh: true` after a re-run) to report why. - Version/fallback: Actions endpoints require **Forgejo v16+**. If `forgejo_action_runs` errors (e.g. 404 — instance predates v16 or Actions disabled) → fall back to the web UI. Non-Actions CI (commit statuses from external CI) is invisible to the extension → web UI. - Caching: logs are cache-first; run metadata is live. Behavior change (generic merge policy, both skills): **all authorised merges wait for green** — when merging is authorised and CI is still running, poll `forgejo_action_runs` up to 15 minutes, then merge on success / stop-and-report on failure, cancelled, or timeout. No runs → "none configured" → merge. Ships as one PR touching both skills + `CHANGELOG.md` (Unreleased → Changed).

david added the

enhancement

label

2026-08-30 04:16:45 +00:00

david referenced this issue from a pull request that will close it,

2026-08-30 04:18:14 +00:00

issue-129: commit-docs/commit-changes check Forgejo CI via the forgejo extension before merging #130

david closed this issue

2026-08-30 04:26:43 +00:00