ci: fix Forgejo LuaRocks publishing #23
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/http-codes.nvim!23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/fix-forgejo-luarocks-tag-release"
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 Forgejo LuaRocks tag workflow invokes
luarocks-tag-releasedirectly withnix run, so it misses composite-action input defaults. The upstream template also assumes GitHub archive directories, while Forgejo archives unpack as the repository name.Solution
Add a Forgejo-specific rockspec template, pass the required action inputs explicitly, and wait for main-push quality before publishing tagged LuaRocks releases.