Paul Schneider 10f37ac004 drop github.* context, switch to forgejo.* + FORGEJO_TOKEN env var ... The github context was kept for compatibility in yavsc's .forgejo/workflows/release.yml, but we don't need that here — the forgejo context is canonical and we want zero GitHub-flavoured naming in this script. - All ${{ github.* }} -> ${{ forgejo.* }} - Env vars GITHUB_API_URL / GITHUB_REPOSITORY / GITHUB_TOKEN -> FORGEJO_API_URL / FORGEJO_REPOSITORY / FORGEJO_TOKEN - The token's source (${{ secrets.GITHUB_TOKEN }}) is the one exception: that's the runtime variable name exposed by the upstream Action runner, not a naming choice. A comment in the env block explains why we read it under the legacy name and immediately re-bind it to FORGEJO_TOKEN. - Same for $GITHUB_ENV (inter-step env file): runtime-controlled name, kept under its technical identity with a note. YAML re-validated with yaml.safe_load.		2026-08-17 16:02:58 +01:00
..
release.yml	drop github.* context, switch to forgejo.* + FORGEJO_TOKEN env var	2026-08-17 16:02:58 +01:00