barrettruth/http-codes.nvim
1
0
Fork 0
Code Issues Pull requests Releases Packages Activity Actions

ci: use Forgejo LuaRocks action #26

Merged
barrettruth merged 1 commit from ci/use-forgejo-luarocks-action-v013 into main 2026-05-03 18:38:17 +00:00
Conversation 0 Commits 1 Files changed 5 +65 -305
barrettruth commented 2026-05-03 18:35:41 +00:00
Owner
Copy link

Problem

The stable and nightly LuaRocks workflows still use repo-local publishing scripts from the pre-action migration. That duplicates publishing behavior now handled by barrettruth/luarocks-tag-release-forgejo, and the old nightly job name renders as deploy / Nightly LuaRocks instead of the current deploy / Nightly convention.

Solution

Replace the repo-local publishing scripts with barrettruth/luarocks-tag-release-forgejo@v0.1.3, the cp.nvim-verified action version that keeps SCM rocks on Forgejo archive URLs instead of native git://. Keep stable and nightly as separate event-specific workflow files, share the quality gate through .forgejo/scripts/wait-for-quality.sh, render stable as deploy / LuaRocks, and render nightly as deploy / Nightly.

Validation:

  • bash -n .forgejo/scripts/wait-for-quality.sh
  • parsed .forgejo/workflows/*.yaml with PyYAML via Nix
  • git diff --check
## Problem The stable and nightly LuaRocks workflows still use repo-local publishing scripts from the pre-action migration. That duplicates publishing behavior now handled by `barrettruth/luarocks-tag-release-forgejo`, and the old nightly job name renders as `deploy / Nightly LuaRocks` instead of the current `deploy / Nightly` convention. ## Solution Replace the repo-local publishing scripts with `barrettruth/luarocks-tag-release-forgejo@v0.1.3`, the cp.nvim-verified action version that keeps SCM rocks on Forgejo archive URLs instead of native `git://`. Keep stable and nightly as separate event-specific workflow files, share the quality gate through `.forgejo/scripts/wait-for-quality.sh`, render stable as `deploy / LuaRocks`, and render nightly as `deploy / Nightly`. Validation: - `bash -n .forgejo/scripts/wait-for-quality.sh` - parsed `.forgejo/workflows/*.yaml` with PyYAML via Nix - `git diff --check`
ci: use Forgejo LuaRocks action
All checks were successful
quality / Format (pull_request) Successful in 12s
Details
quality / Lint (pull_request) Successful in 8s
Details
69e8a17160
barrettruth deleted branch ci/use-forgejo-luarocks-action-v013 2026-05-03 18:38:17 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/http-codes.nvim!26
No description provided.