[ISSUE-139] Fix portainer_automation_build_push workflow not registering on test branch #147

Dave · 2026-07-09T05:02:38Z

Dave commented

2026-07-09 05:02:38 +00:00

Summary

Fix portainer_automation_build_push.yml workflow not being registered/available on the test branch.

Root cause: The workflow_dispatch input used type: choice with options: [test, prod]. The Gitea Actions runner in this instance may not support the choice type with the options subfield, causing the entire workflow to silently fail registration.

Fix: Changed the input type from choice to string. The workflow already has runtime validation (lines 40-44) that validates the environment value and fails early with a clear error if it's not test or prod, so the UI-level choice constraint was redundant.

Evidence

integration_test.yaml uses bare workflow_dispatch: (no inputs) — proven working
This is the only workflow using type: choice with options: in its workflow_dispatch inputs
YAML syntax is valid; the file exists on the test branch
A simple push didn't re-register it — suggesting a runner-side parsing/registration issue

Testing

After merge, verify workflow appears in Gitea Actions UI on test branch
Trigger workflow_dispatch manually with environment: test — should run normally
Push to test branch — should trigger automatically as before

Issues

Hithomelabs/CFTunnels#139

## Summary Fix `portainer_automation_build_push.yml` workflow not being registered/available on the `test` branch. **Root cause**: The `workflow_dispatch` input used `type: choice` with `options: [test, prod]`. The Gitea Actions runner in this instance may not support the `choice` type with the `options` subfield, causing the entire workflow to silently fail registration. **Fix**: Changed the input `type` from `choice` to `string`. The workflow already has runtime validation (lines 40-44) that validates the environment value and fails early with a clear error if it's not `test` or `prod`, so the UI-level `choice` constraint was redundant. ## Evidence - `integration_test.yaml` uses bare `workflow_dispatch:` (no inputs) — proven working - This is the **only** workflow using `type: choice` with `options:` in its `workflow_dispatch` inputs - YAML syntax is valid; the file exists on the `test` branch - A simple push didn't re-register it — suggesting a runner-side parsing/registration issue ## Testing - [ ] After merge, verify workflow appears in Gitea Actions UI on `test` branch - [ ] Trigger `workflow_dispatch` manually with `environment: test` — should run normally - [ ] Push to `test` branch — should trigger automatically as before ## Issues - Hithomelabs/CFTunnels#139