static-site-deploy/tests
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Eric Wendland c242db40a1
All checks were successful
Test / test (push) Successful in 9s
feat(static-site-deploy): deploy with the workflow's OIDC identity
Without BUNNY_STORAGE_PASSWORD, the action now requests the running
workflow's OIDC identity token (Forgejo with enable-openid-connect,
GitHub with id-token: write) for the gateway's audience and starts the
deployment with it. It takes the Storage Zone password from the
gateway's answer, masks it in the log, plans and uploads with it, and
finalizes or aborts with a fresh token. A dry run in this mode stays
local. Password deployments work as before.

action.yml finds its script under FORGEJO_ACTION_PATH or
GITHUB_ACTION_PATH, so the action also runs on GitHub Actions.
2026-10-02 23:29:58 +02:00
..
test_static_site.py feat(static-site-deploy): deploy with the workflow's OIDC identity 2026-10-02 23:29:58 +02:00