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

Merged

hitanshu merged 2 commits from Dave/CFTunnels:ISSUE-139-fix-workflow-registration into test

2026-07-09 05:09:29 +00:00

Author	SHA1	Message	Date
Dave the Dev	8ee2abdbd7	Hithomelabs/CFTunnels#139 : Remove portainer-automation service from docker-compose.yaml (now managed independently via portainer-automation/docker-compose.yaml) All checks were successful sample gradle build and test / build (pull_request) Successful in 1m58s Details Daily cloudflare API integration test / cloudflare-api-test (push) Successful in 1m49s Details Promote image with tag test to prod / tag (push) Successful in 6s Details Promote image with tag test to prod / build_tag_push (push) Successful in 13s Details sample gradle build and test / tag (push) Successful in 7s Details sample gradle build and test / build_tag_push (push) Successful in 2m30s Details	2026-07-09 05:04:48 +00:00
hitanshu310	35db41573a	Hithomelabs/CFTunnels#139 : Simplify workflow_dispatch input type for Gitea compatibility Some checks failed sample gradle build and test / build (pull_request) Has been cancelled Details Remove 'type: choice' and 'options:' from workflow_dispatch inputs, replacing with 'type: string'. The Gitea Actions runner may not support the 'choice' type with 'options' subfield, causing the entire workflow to fail registration silently. The workflow already has runtime validation (lines 40-44) that rejects invalid environment values, so the 'choice' type was redundant.	2026-07-09 10:32:26 +05:30