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

fix(ci): put LuaRocks publishing under deploy workflow #21

Merged
barrettruth merged 1 commit from ci/deploy-luarocks-context into main 2026-05-03 16:49:20 +00:00
Conversation 0 Commits 1 Files changed 1 +2 -2
barrettruth commented 2026-05-03 16:46:01 +00:00
Owner
Copy link

Problem
The LuaRocks publish workflow currently uses the workflow prefix luarocks, so tag-publish status contexts render as luarocks / Publish to LuaRocks. Publish/deploy jobs should live under the deploy namespace, matching the newer deploy/nightly naming strategy.

Solution
Rename the LuaRocks workflow and job display names so future tag-publish contexts render as:

  • deploy / LuaRocks

The tag trigger, job id, runner, secret usage, and publish command are unchanged.

Verification

  • Parsed .forgejo/workflows/luarocks.yaml with PyYAML.
  • Ran git diff --check.
Problem The LuaRocks publish workflow currently uses the workflow prefix `luarocks`, so tag-publish status contexts render as `luarocks / Publish to LuaRocks`. Publish/deploy jobs should live under the deploy namespace, matching the newer deploy/nightly naming strategy. Solution Rename the LuaRocks workflow and job display names so future tag-publish contexts render as: - deploy / LuaRocks The tag trigger, job id, runner, secret usage, and publish command are unchanged. Verification - Parsed `.forgejo/workflows/luarocks.yaml` with PyYAML. - Ran `git diff --check`.
fix(ci): put LuaRocks publishing under deploy workflow
All checks were successful
quality / Format (pull_request) Successful in 10s
Details
quality / Lint (pull_request) Successful in 5s
Details
3b8b444552
barrettruth deleted branch ci/deploy-luarocks-context 2026-05-03 16:49:20 +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!21
No description provided.