fix(ci): gate deploy on quality checks #13

Merged

barrettruth merged 1 commit from ci/gate-publish-on-quality into main

2026-05-03 16:07:17 +00:00

barrettruth commented

2026-05-03 16:04:16 +00:00

Owner

Problem
The deploy workflow starts on the same main-branch push as the quality workflow, so production deploy can begin before Format, Lint, and Build have all finished successfully.

Solution
Add a deploy-side wait gate that polls the Forgejo commit status API for the main-push quality contexts:

quality / Format (push)
quality / Lint (push)
quality / Build (push)

The deploy job is also restricted to refs/heads/main so manual dispatches do not deploy arbitrary branches.

Verification

Parsed all changed Forgejo workflow YAML with PyYAML.
Ran node --check on the embedded wait script.
Ran git diff --check.

Problem The deploy workflow starts on the same main-branch push as the quality workflow, so production deploy can begin before Format, Lint, and Build have all finished successfully. Solution Add a deploy-side wait gate that polls the Forgejo commit status API for the main-push quality contexts: - quality / Format (push) - quality / Lint (push) - quality / Build (push) The deploy job is also restricted to refs/heads/main so manual dispatches do not deploy arbitrary branches. Verification - Parsed all changed Forgejo workflow YAML with PyYAML. - Ran node --check on the embedded wait script. - Ran git diff --check.

barrettruth added 1 commit

2026-05-03 16:04:16 +00:00

fix(ci): gate deploy on quality checks

quality / Format (pull_request) Successful in 9s

Details

quality / Lint (pull_request) Successful in 16s

Details

quality / Build (pull_request) Successful in 23s

Details

d338230983