ci: align actions/* references with code.forgejo.org mirror #2

Merged
pappi merged 1 commit from agent/fix-actions-resolution into main 2026-05-09 15:59:15 +00:00
Owner

What

Aligns this repo's .forgejo/workflows/branch-policy.yml with the
canonical template now on automation/main:

  • uses: actions/checkout@v4uses: https://code.forgejo.org/actions/checkout@v4
  • uses: actions/setup-node@v4uses: https://code.forgejo.org/actions/setup-node@v4

Also updates the branch-protection required-status-check name from
branch-policy to the actual Forgejo Actions context
Branch policy / branch-policy (pull_request) so merges aren't
falsely blocked despite green CI.

Why

Forgejo Actions resolves bare actions/<name> against the local
Forgejo instance, which has no actions/* org. Every PR's
branch-policy CI was failing in ~1s with 404 on
/actions/checkout/info/refs. Switching to full URLs at
code.forgejo.org (the official Forgejo Actions mirror) fixes the
resolution.

The required-check rename matches the Forgejo Actions context
format (<workflow_name>/<job_id> (<event>)) — protection still
gates on the same single check, just under its actual reported
name.

Companion to automation #3
(ci(forgejo): bundle runner-and-actions infrastructure fixes),
which landed the canonical template + role defaults updates and
the runner-recovery runbook.

How verified

  • Workflow file copied byte-for-byte from
    automation/forgejo/templates/branch-policy/.forgejo/workflows/branch-policy.yml
    on automation/main (the canonical source).
  • This PR's branch-policy CI runs against the head branch's
    workflow, which has the fix in place. CI passing here is the live
    proof the fix works for this repo.

Refs: B3, automation #3.

## What Aligns this repo's `.forgejo/workflows/branch-policy.yml` with the canonical template now on `automation/main`: - `uses: actions/checkout@v4` → `uses: https://code.forgejo.org/actions/checkout@v4` - `uses: actions/setup-node@v4` → `uses: https://code.forgejo.org/actions/setup-node@v4` Also updates the branch-protection required-status-check name from `branch-policy` to the actual Forgejo Actions context `Branch policy / branch-policy (pull_request)` so merges aren't falsely blocked despite green CI. ## Why Forgejo Actions resolves bare `actions/<name>` against the local Forgejo instance, which has no `actions/*` org. Every PR's branch-policy CI was failing in ~1s with 404 on `/actions/checkout/info/refs`. Switching to full URLs at `code.forgejo.org` (the official Forgejo Actions mirror) fixes the resolution. The required-check rename matches the Forgejo Actions context format (`<workflow_name>/<job_id> (<event>)`) — protection still gates on the same single check, just under its actual reported name. Companion to automation #3 (`ci(forgejo): bundle runner-and-actions infrastructure fixes`), which landed the canonical template + role defaults updates and the runner-recovery runbook. ## How verified - Workflow file copied byte-for-byte from `automation/forgejo/templates/branch-policy/.forgejo/workflows/branch-policy.yml` on `automation/main` (the canonical source). - This PR's `branch-policy` CI runs against the head branch's workflow, which has the fix in place. CI passing here is the live proof the fix works for this repo. --- Refs: B3, automation #3.
ci: align actions/* references with code.forgejo.org mirror
All checks were successful
Branch policy / branch-policy (pull_request) Successful in 39s
22acda097f
pappi merged commit 131ccd5910 into main 2026-05-09 15:59:15 +00:00
Sign in to join this conversation.
No reviewers
No labels
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
hanuman/verticals!2
No description provided.