ci: consolidate deploy workflow #24
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!24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/consolidate-deploy-workflow"
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
LuaRocks stable and nightly deploys are still split across
.forgejo/workflows/luarocks.yamland.forgejo/workflows/luarocks-nightly.yaml, even though both are one deploy surface and already share the same quality gate/action.Solution
Replace both files with
.forgejo/workflows/deploy.yaml. The workflow uses one publish job with a dynamic job name, so main pushes render asdeploy / Nightlyand tag pushes render asdeploy / LuaRockswithout keeping two workflow files. Step-level conditions select the nightly or stable LuaRocks publish path.Validation:
bash -n .forgejo/scripts/wait-for-quality.sh.forgejo/workflows/*.yamlwith PyYAML via Nixgit diff --check