fix(ci): restore gated deploy workflow #265

Merged
barrettruth merged 1 commit from ci/gate-publish-on-quality into main 2026-05-03 16:07:27 +00:00
Owner

Problem
The pre-Forgejo GitHub CI workflow had a Deploy job, but the Forgejo port dropped non-quality workflows and left only .forgejo/workflows/quality.yaml. That means delta no longer has a Forgejo deploy workflow to gate on quality.

Solution
Restore a Forgejo deploy workflow that waits for the main-push quality contexts before SSHing to the VPS and running /opt/delta/scripts/deploy.sh:

  • quality / Lint (push)
  • quality / Test (push)
  • quality / Build (push)

The deploy step keeps the previous deploy-secret shape: VPS_HOST, VPS_USERNAME, and VPS_SSH_KEY.

Verification

  • Parsed all changed Forgejo workflow YAML with PyYAML.
  • Ran node --check on the embedded wait script.
  • Ran git diff --check.
Problem The pre-Forgejo GitHub CI workflow had a Deploy job, but the Forgejo port dropped non-quality workflows and left only .forgejo/workflows/quality.yaml. That means delta no longer has a Forgejo deploy workflow to gate on quality. Solution Restore a Forgejo deploy workflow that waits for the main-push quality contexts before SSHing to the VPS and running /opt/delta/scripts/deploy.sh: - quality / Lint (push) - quality / Test (push) - quality / Build (push) The deploy step keeps the previous deploy-secret shape: VPS_HOST, VPS_USERNAME, and VPS_SSH_KEY. Verification - Parsed all changed Forgejo workflow YAML with PyYAML. - Ran node --check on the embedded wait script. - Ran git diff --check.
fix(ci): restore gated deploy workflow
All checks were successful
quality / Test (pull_request) Successful in 30s
quality / Lint (pull_request) Successful in 39s
quality / Build (pull_request) Successful in 1m11s
cb324a7255
barrettruth deleted branch ci/gate-publish-on-quality 2026-05-03 16:07:27 +00:00
Sign in to join this conversation.
No description provided.