ci: use Forgejo-native action context #7

Merged
barrettruth merged 1 commit from ci/forgejo-native-action-context into main 2026-05-05 18:15:17 +00:00
Owner

Checklist

  • I have read CONTRIBUTING.md.
  • No AI was used to generate, edit, or review any part of this contribution.

Problem

Forgejo exposes native ${{ forgejo.* }} context and FORGEJO_* environment variables, but this action still read GitHub compatibility aliases in its composite metadata and Lua entrypoint.

Solution

Use Forgejo-native action context in action.yml, read FORGEJO_* variables in the action entrypoint, and rename internal event/repository metadata from GitHub to Forgejo terminology.

Verification

  • nix develop --accept-flake-config .#ci --command just ci
  • rg -n 'GITHUB_|\\$\\{\\{[[:space:]]*github\\.|Github|github_' action.yml bin lua spec .forgejo
## Checklist - [x] I have read [CONTRIBUTING.md](https://git.barrettruth.com/barrettruth/luarocks-tag-release-forgejo/src/branch/main/CONTRIBUTING.md). - [ ] No AI was used to generate, edit, or review any part of this contribution. ## Problem Forgejo exposes native `${{ forgejo.* }}` context and `FORGEJO_*` environment variables, but this action still read GitHub compatibility aliases in its composite metadata and Lua entrypoint. ## Solution Use Forgejo-native action context in `action.yml`, read `FORGEJO_*` variables in the action entrypoint, and rename internal event/repository metadata from GitHub to Forgejo terminology. ## Verification - `nix develop --accept-flake-config .#ci --command just ci` - `rg -n 'GITHUB_|\\$\\{\\{[[:space:]]*github\\.|Github|github_' action.yml bin lua spec .forgejo`
ci: use Forgejo-native action context
All checks were successful
quality / Lint (pull_request) Successful in 5s
quality / Build aarch64 (pull_request) Successful in 7s
quality / Format (pull_request) Successful in 7s
quality / Test (pull_request) Successful in 11s
a5c973bbc0
barrettruth deleted branch ci/forgejo-native-action-context 2026-05-05 18:15:17 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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/luarocks-tag-release-forgejo!7
No description provided.