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

Merged

david merged 1 commit from feature/issue-129/forgejo-ci-check into main

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

david commented

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

Owner

Both commit skills told agents "the extension doesn't surface CI — check the web UI; same for fj" before merging. That's stale: the forgejo pi extension now ships read-only Forgejo Actions tools that surface CI directly. This PR replaces the stale line with a proper how-to and tightens the merge gate.

What & why

"Checking CI on Forgejo" subsection (both skills): check the PR's Actions runs via forgejo_action_runs head_sha=<PR head sha> (primary filter — catches push AND pull_request-event runs, robust for fork PRs), with ref: refs/heads/<branch> noted as a lighter alternative. Aggregation: any failure → failing; any running/waiting → running; all success → success; none → "none configured" (gate passes). On failure: forgejo_action_jobs → forgejo_action_job_log (refresh: true after re-runs; logs are cache-first).
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.
Wait-for-green merge gate (generic, host-agnostic wording): when merging is authorised (explicit instruction OR a "yes" to the merge prompt) and CI is still running, wait for green — poll forgejo_action_runs up to 15 minutes, then merge on success / stop-and-report on failure, cancellation, or timeout. No runs → "none configured" → merge. GitHub/GitLab get no new CI-check instructions.

Per-file breakdown

skills/commit-docs/SKILL.md (modified): new "Checking CI on Forgejo" section; Step 4 CI-check line now points at the extension (web-UI fallback noted); merge-policy gate wording → wait-for-green; Failure Handling gains a "CI still running on an authorised merge" entry; Quick Reference updated.
skills/commit-changes/SKILL.md (modified): identical changes in Step 5, merge policy, Failure Handling table, and both Quick Reference blocks.
CHANGELOG.md (modified): Unreleased → Changed entry.

Closes #129

Both commit skills told agents *"the extension doesn't surface CI — check the web UI; same for `fj`"* before merging. That's stale: the `forgejo` pi extension now ships read-only Forgejo Actions tools that surface CI directly. This PR replaces the stale line with a proper how-to and tightens the merge gate. **What & why** - **"Checking CI on Forgejo" subsection** (both skills): check the PR's Actions runs via `forgejo_action_runs head_sha=<PR head sha>` (primary filter — catches push AND pull_request-event runs, robust for fork PRs), with `ref: refs/heads/<branch>` noted as a lighter alternative. Aggregation: any failure → failing; any running/waiting → running; all success → success; none → "none configured" (gate passes). On failure: `forgejo_action_jobs` → `forgejo_action_job_log` (`refresh: true` after re-runs; logs are cache-first). - **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. - **Wait-for-green merge gate (generic, host-agnostic wording)**: when merging is authorised (explicit instruction OR a "yes" to the merge prompt) and CI is still running, wait for green — poll `forgejo_action_runs` up to 15 minutes, then merge on success / stop-and-report on failure, cancellation, or timeout. No runs → "none configured" → merge. GitHub/GitLab get no new CI-check instructions. **Per-file breakdown** - `skills/commit-docs/SKILL.md` (modified): new "Checking CI on Forgejo" section; Step 4 CI-check line now points at the extension (web-UI fallback noted); merge-policy gate wording → wait-for-green; Failure Handling gains a "CI still running on an authorised merge" entry; Quick Reference updated. - `skills/commit-changes/SKILL.md` (modified): identical changes in Step 5, merge policy, Failure Handling table, and both Quick Reference blocks. - `CHANGELOG.md` (modified): Unreleased → Changed entry. Closes #129

david added the

enhancement

label

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

david added 1 commit

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