Fix Forgejo reusable workflow compatibility
Some checks failed
Publish Hugo Deployment Image / publish (push) Failing after 5s
Some checks failed
Publish Hugo Deployment Image / publish (push) Failing after 5s
This commit is contained in:
parent
28fb445eaf
commit
50ddaa6fce
1 changed files with 2 additions and 4 deletions
|
|
@ -66,6 +66,7 @@ jobs:
|
|||
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
|
||||
- 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
|
||||
- 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`
|
||||
|
|
|
|||
Loading…
Reference in a new issue