ci: split LuaRocks deploy triggers #21

Merged

barrettruth merged 1 commit from ci/split-luarocks-deploy-triggers into main

2026-05-04 00:15:55 +00:00

barrettruth commented

2026-05-04 00:07:13 +00:00

Owner

Problem

The consolidated LuaRocks deploy workflow uses one dynamically named job for both stable tag releases and main-push nightly releases. Forgejo can render the wrong context for main-push nightly runs, and job-level conditions can leak skipped stable-release contexts.

Solution

Keep the rendered workflow prefix as deploy, but split the triggers by workflow file. deploy.yaml is now tag-only and renders deploy / LuaRocks; deploy-nightly.yaml handles main pushes/manual nightly runs and renders deploy / LuaRocks (nightly). The nightly publish job keeps the existing quality-status polling inside the publish job, so no visible quality-gate context is added.

Problem The consolidated LuaRocks deploy workflow uses one dynamically named job for both stable tag releases and main-push nightly releases. Forgejo can render the wrong context for main-push nightly runs, and job-level conditions can leak skipped stable-release contexts. Solution Keep the rendered workflow prefix as `deploy`, but split the triggers by workflow file. `deploy.yaml` is now tag-only and renders `deploy / LuaRocks`; `deploy-nightly.yaml` handles main pushes/manual nightly runs and renders `deploy / LuaRocks (nightly)`. The nightly publish job keeps the existing quality-status polling inside the publish job, so no visible quality-gate context is added.

barrettruth added 1 commit

2026-05-04 00:07:13 +00:00

ci: split LuaRocks deploy triggers

quality / Format (pull_request) Successful in 4s

Details

quality / Lint (pull_request) Successful in 5s

Details

quality / Test (pull_request) Successful in 3s

Details

eaf24f29d5