ci: split LuaRocks deploy jobs #27
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/blink-cmp-ghostty!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/static-luarocks-deploy-jobs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The consolidated deploy job uses a dynamic job name to choose between
LuaRocksandLuaRocks (nightly). Forgejo runs the correct step on main, but the rendered status context can still showdeploy / LuaRocksfor a nightly main-push run.Solution
Keep a single
deploy.yaml, but split the publish job into two statically named jobs guarded by ref-specific job conditions:LuaRocksforv*tags andLuaRocks (nightly)formainpushes. This removes the ref-dependent job-name expression while preserving the stable and nightly publish paths.