ci: fix deploy job name expression #28

Merged

barrettruth merged 1 commit from ci/fix-deploy-job-name into main

2026-05-03 19:01:20 +00:00

barrettruth commented

2026-05-03 18:59:25 +00:00

Owner

Problem

The consolidated deploy workflow uses one publish job with a dynamic job name. On main pushes, Forgejo rendered the job as deploy / LuaRocks instead of deploy / Nightly, even though the step-level github.ref conditions still selected the correct publish path.

Solution

Use github.ref for the job-name expression, matching the step conditions and the runner-provided compatibility context. This keeps the one-file deploy.yaml layout while preserving the expected rendered names.

Validation:

parsed .forgejo/workflows/*.yaml with PyYAML via Nix
git diff --check

## Problem The consolidated deploy workflow uses one publish job with a dynamic job name. On main pushes, Forgejo rendered the job as `deploy / LuaRocks` instead of `deploy / Nightly`, even though the step-level `github.ref` conditions still selected the correct publish path. ## Solution Use `github.ref` for the job-name expression, matching the step conditions and the runner-provided compatibility context. This keeps the one-file `deploy.yaml` layout while preserving the expected rendered names. Validation: - parsed `.forgejo/workflows/*.yaml` with PyYAML via Nix - `git diff --check`

barrettruth added 1 commit

2026-05-03 18:59:25 +00:00

ci: fix deploy job name expression

quality / Format (pull_request) Successful in 13s

Details

quality / Lint (pull_request) Successful in 11s

Details

4f62e4cd60