cliper/hugo_deployment
Watch
1
0
Fork
You've already forked hugo_deployment
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix Forgejo reusable workflow compatibility
Some checks failed
Publish Hugo Deployment Image / publish (push) Failing after 5s
Details

Browse source
This commit is contained in:
Neil Borromeo 2026-04-19 13:23:45 +08:00
commit 50ddaa6fce
2 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

5
.forgejo/workflows/deploy-hugo-site.yml
View file

@ -28,9 +28,6 @@ on:
required: false required: false
default: "" default: ""
type: string type: string
secrets:
deploy_ssh_key:
required: true
jobs: jobs:
deploy: deploy:
@ -50,7 +47,7 @@ jobs:
DEPLOY_PATH: ${{ vars.DEPLOY_PATH }} DEPLOY_PATH: ${{ vars.DEPLOY_PATH }}
HUGO_PARAMS_ANALYTICS_GOOGLE_SITEVERIFICATIONTAG: ${{ vars.GOOGLE_SITE_VERIFICATION_TAG }} HUGO_PARAMS_ANALYTICS_GOOGLE_SITEVERIFICATIONTAG: ${{ vars.GOOGLE_SITE_VERIFICATION_TAG }}
HUGO_PARAMS_TURNSTILESITEKEY: ${{ vars.TURNSTILE_SITE_KEY }} HUGO_PARAMS_TURNSTILESITEKEY: ${{ vars.TURNSTILE_SITE_KEY }}
HUGO_WORKER_URL: ${{ vars.WORKER_URL }} HUGO_WORKER_URL: ${{ vars.HUGO_WORKER_URL }}
steps: steps:
- name: Checkout repository - name: Checkout repository
uses: https://data.forgejo.org/actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 uses: https://data.forgejo.org/actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5

1
README.md
View file

@ -66,6 +66,7 @@ jobs:
Notes: Notes:
- For the current caller pattern, `DEPLOY_SSH_HOST`, `DEPLOY_SSH_USER`, and `DEPLOY_PATH` are required repo variables unless the caller explicitly passes host and user as workflow inputs - For the current caller pattern, `DEPLOY_SSH_HOST`, `DEPLOY_SSH_USER`, and `DEPLOY_PATH` are required repo variables unless the caller explicitly passes host and user as workflow inputs
- Caller repos pass `DEPLOY_SSH_KEY` through `jobs.<job_id>.secrets`; Forgejo v11 accepts caller-provided reusable workflow secrets even though `on.workflow_call` itself only documents `inputs` and `outputs`
- Caller repos can set `DEPLOY_KNOWN_HOSTS` in repo variables with a pinned `known_hosts` entry for stronger host verification - Caller repos can set `DEPLOY_KNOWN_HOSTS` in repo variables with a pinned `known_hosts` entry for stronger host verification
- If `DEPLOY_KNOWN_HOSTS` is not set, the workflow falls back to `ssh-keyscan` so current repos keep working - If `DEPLOY_KNOWN_HOSTS` is not set, the workflow falls back to `ssh-keyscan` so current repos keep working
- The reusable workflow itself always runs on `docker-desktop` - The reusable workflow itself always runs on `docker-desktop`