quartz-pages: run Pages steps and deploy only on the GitHub mirror #4

Closed
void wants to merge 2 commits from void/pages-gate into main AGit
Member

Cause: the shared workflow uses GitHub-only Pages actions. On the forge runner (Forgejo 16.0.3, runner v13.2.0, single slot) actions resolve from data.forgejo.org, which has no actions/configure-pages. AetheriaLore run 791 (build job, log build-1651):

unable to probe object format for https://data.forgejo.org/actions/configure-pages: ls-remote failed ... fatal: repository 'https://data.forgejo.org/actions/configure-pages/' not found then Job failed; the deploy job never starts.

Change (6 lines, one file): if: github.server_url == 'https://github.com' on the Configure Pages step, the Upload Pages artifact step and the whole deploy job. Checkout, setup-node, npm ci and the Quartz build still run everywhere, so a forge run becomes a real build check instead of a failure.

Verified context: AetheriaLore PR #6 (Weksa, same condition at the caller's deploy job) was merged and its push run 938 on the forge has job deploy and its called jobs build/deploy-1 all skipped, so the forge evaluates github.server_url == 'https://github.com' to false. Run 791 (before the gate) shows the runner's event as workflow_call and the same forge host. I did not see the literal server_url value printed; the skip is the evidence.

Concurrency: deliberately not added here. Consumers already declare concurrency: group: pages at the caller; a callee declaring the same group deadlocks/cancels itself on GitHub, and a different group would add nothing. Note the consumers set cancel-in-progress: true, which can cancel an in-flight Pages deploy; that is a consumer-side choice (false for a deploy group).

Not run: no run of this branch (the workflow is only invoked via workflow_call from consumers, @main; it takes effect after merge); GitHub-side behaviour untested here; YAML parse checked with python yaml only.

Not merged.

🤖 Generated with Claude Code

Cause: the shared workflow uses GitHub-only Pages actions. On the forge runner (Forgejo 16.0.3, runner v13.2.0, single slot) actions resolve from data.forgejo.org, which has no actions/configure-pages. AetheriaLore run 791 (build job, log build-1651): `unable to probe object format for https://data.forgejo.org/actions/configure-pages: ls-remote failed ... fatal: repository 'https://data.forgejo.org/actions/configure-pages/' not found` then `Job failed`; the deploy job never starts. Change (6 lines, one file): `if: github.server_url == 'https://github.com'` on the Configure Pages step, the Upload Pages artifact step and the whole `deploy` job. Checkout, setup-node, npm ci and the Quartz build still run everywhere, so a forge run becomes a real build check instead of a failure. Verified context: AetheriaLore PR #6 (Weksa, same condition at the caller's `deploy` job) was merged and its push run 938 on the forge has job `deploy` and its called jobs `build`/`deploy-1` all `skipped`, so the forge evaluates `github.server_url == 'https://github.com'` to false. Run 791 (before the gate) shows the runner's event as workflow_call and the same forge host. I did not see the literal server_url value printed; the skip is the evidence. Concurrency: deliberately not added here. Consumers already declare `concurrency: group: pages` at the caller; a callee declaring the same group deadlocks/cancels itself on GitHub, and a different group would add nothing. Note the consumers set cancel-in-progress: true, which can cancel an in-flight Pages deploy; that is a consumer-side choice (false for a deploy group). Not run: no run of this branch (the workflow is only invoked via workflow_call from consumers, @main; it takes effect after merge); GitHub-side behaviour untested here; YAML parse checked with python yaml only. Not merged. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
quartz-pages: Pages steps and deploy job run only on the GitHub mirror
Some checks failed
Engine CI / build-and-test (docker) (pull_request) Has been cancelled
484dfc4911
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
TEMP: throwaway caller to exercise quartz-pages guards (removed next commit)
Some checks failed
Engine CI / build-and-test (docker) (pull_request) Successful in 3m11s
throwaway gate test / build (pull_request) Failing after 1s
throwaway gate test / deploy (pull_request) Has been skipped
throwaway gate test / test (pull_request) Failing after 0s
a7a4ff3aef
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Author
Member

Superseded by #6, which carries only the github.server_url guard from void/pages-gate. Closing this one: its head was stale and its branch deleted.

Superseded by #6, which carries only the github.server_url guard from void/pages-gate. Closing this one: its head was stale and its branch deleted.
void closed this pull request 2026-11-11 10:59:09 +00:00
Some checks failed
Engine CI / build-and-test (docker) (pull_request) Successful in 3m11s
throwaway gate test / build (pull_request) Failing after 1s
throwaway gate test / deploy (pull_request) Has been skipped
throwaway gate test / test (pull_request) Failing after 0s

Pull request closed

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
GameCult/GameCult-Quartz!4
No description provided.