ci: separate LuaRocks deploy triggers #28

Merged

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

2026-05-03 23:31:06 +00:00

barrettruth commented

2026-05-03 23:24:45 +00:00

Owner

Problem

The two-job single-file deploy experiment still creates both status contexts on main pushes. Forgejo queues both jobs first, then marks the stable LuaRocks job skipped, which still leaves an unwanted deploy / LuaRocks status on main.

Solution

Keep both rendered workflow prefixes as deploy, but split stable and nightly publishing by event trigger. deploy.yaml now only handles v* tag pushes with LuaRocks; deploy-nightly.yaml handles main pushes and manual nightly runs with LuaRocks (nightly). This lets Forgejo instantiate only the workflow that matches the event instead of relying on job-level skips.

Problem The two-job single-file deploy experiment still creates both status contexts on main pushes. Forgejo queues both jobs first, then marks the stable LuaRocks job skipped, which still leaves an unwanted `deploy / LuaRocks` status on main. Solution Keep both rendered workflow prefixes as `deploy`, but split stable and nightly publishing by event trigger. `deploy.yaml` now only handles `v*` tag pushes with `LuaRocks`; `deploy-nightly.yaml` handles main pushes and manual nightly runs with `LuaRocks (nightly)`. This lets Forgejo instantiate only the workflow that matches the event instead of relying on job-level skips.

barrettruth added 1 commit

2026-05-03 23:24:45 +00:00

ci: separate LuaRocks deploy triggers

quality / Test (pull_request) Successful in 4s

Details

quality / Format (pull_request) Successful in 5s

Details

quality / Lint (pull_request) Successful in 4s

Details

179d065d22