Fix Forgejo deploy form: add type string to version input.
Forgejo workflow_dispatch requires an explicit input type; without it the UI showed invalidinputtype. Clarify README: workflow ref vs version tag. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
parent
de86880a8f
commit
082139d266
2 changed files with 5 additions and 2 deletions
|
|
@ -4,9 +4,10 @@ on:
|
|||
workflow_dispatch:
|
||||
inputs:
|
||||
version:
|
||||
description: 'Version tag (e.g., v0.1.0)'
|
||||
description: 'Git tag to create for this deploy (e.g. v0.1.2) — not the branch/tag above'
|
||||
required: true
|
||||
default: 'v0.1.0'
|
||||
type: string
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
|
|
|
|||
|
|
@ -386,7 +386,9 @@ Before the first deploy, complete these steps on the production server (`srvr.nu
|
|||
|
||||
1. Go to **Actions → Deploy to Production** in Forgejo.
|
||||
2. Click **Run workflow**.
|
||||
3. Enter a version tag (e.g., `v0.1.0`).
|
||||
3. Fill in both fields (Forgejo requires `type` on inputs — see `deploy.yml`):
|
||||
- **Use workflow from:** `master` (which commit to build). Do not confuse this with the deploy tag below.
|
||||
- **Version tag:** label created by the pipeline (e.g. `v0.1.2`). Change this each release; default `v0.1.0` is only a placeholder.
|
||||
4. Click **Run workflow**.
|
||||
|
||||
### Deploy failed (backend health check)
|
||||
|
|
|
|||
Loading…
Reference in a new issue