Hithomelabs/CFTunnels
10
0
Fork 4
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

[ISSUE-139] Remove workflow_dispatch inputs for Gitea 1.22.x compatibility #149

Merged
hitanshu merged 2 commits from Dave/CFTunnels:ISSUE-139-remove-inputs into test 2026-07-09 06:15:28 +00:00
Conversation 0 Commits 2 Files Changed 1 +2 -14
Dave commented 2026-07-09 05:44:23 +00:00
Member
Copy Link

Summary

Gitea 1.22.x does NOT support workflow_dispatch with inputs. The inputs block under workflow_dispatch causes the nektos/act YAML parser to silently reject the entire workflow file, so it never appears in the Gitea Actions UI. The push trigger also stops working as a result.

Changes Made

  1. Removed the inputs block entirely from on.workflow_dispatch — now just an empty trigger (workflow_dispatch:).

  2. Simplified the "Determine environment" step to be purely branch-based — removed the if workflow_dispatch / inputs.environment branch. Environment is now determined solely by github.ref_name:

    • Push to main → target_env=prod → MINOR bump
    • Push to test → target_env=test → PATCH bump
    • Manual workflow_dispatch on either branch → same branch-based logic

Behavior After Fix

  • Push to test branch → target_env=test → PATCH bump → build & push test image
  • Push to main branch → target_env=prod → MINOR bump → promote test→prod image
  • Manual workflow_dispatch (on either branch) → same branch-based logic applies
  • The "Run workflow" button will still appear in Gitea Actions UI (just without custom input fields)

Related Issues

Testing

  • Workflow appears in Gitea Actions UI
  • Push to test branch triggers the workflow
  • Manual workflow_dispatch triggers without input fields
## Summary Gitea 1.22.x does NOT support `workflow_dispatch` with `inputs`. The `inputs` block under `workflow_dispatch` causes the `nektos/act` YAML parser to silently reject the entire workflow file, so it never appears in the Gitea Actions UI. The `push` trigger also stops working as a result. ### Changes Made 1. **Removed the `inputs` block entirely from `on.workflow_dispatch`** — now just an empty trigger (`workflow_dispatch:`). 2. **Simplified the "Determine environment" step to be purely branch-based** — removed the `if workflow_dispatch` / `inputs.environment` branch. Environment is now determined solely by `github.ref_name`: - Push to `main` → `target_env=prod` → MINOR bump - Push to `test` → `target_env=test` → PATCH bump - Manual `workflow_dispatch` on either branch → same branch-based logic ### Behavior After Fix - **Push to `test` branch** → `target_env=test` → PATCH bump → build & push test image - **Push to `main` branch** → `target_env=prod` → MINOR bump → promote test→prod image - **Manual `workflow_dispatch`** (on either branch) → same branch-based logic applies - The "Run workflow" button will still appear in Gitea Actions UI (just without custom input fields) ## Related Issues - Hithomelabs/CFTunnels#139 ## Testing - [ ] Workflow appears in Gitea Actions UI - [ ] Push to test branch triggers the workflow - [ ] Manual workflow_dispatch triggers without input fields
Dave added 1 commit 2026-07-09 05:44:24 +00:00
Hithomelabs/CFTunnels#139: Remove workflow_dispatch inputs for Gitea 1.22.x compat
All checks were successful
sample gradle build and test / build (pull_request) Successful in 1m53s
Details
c9dea2a91d
Dave added 1 commit 2026-07-09 06:12:00 +00:00
Hithomelabs/CFTunnels#149: Resolve merge conflicts by removing workflow_dispatch inputs and simplifying env step
Some checks failed
sample gradle build and test / build (pull_request) Successful in 1m51s
Details
Build & Push Portainer Automation / version (push) Successful in 7s
Details
sample gradle build and test / tag (push) Successful in 7s
Details
Build & Push Portainer Automation / build-and-push (push) Successful in 1m55s
Details
sample gradle build and test / build_tag_push (push) Failing after 28s
Details
0df22454a3
hitanshu merged commit 0df22454a3 into test 2026-07-09 06:15:28 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
architect:complete

Architecture analysis completed

  
blocked-by:#139

Blocked by issue #139

  
blocks:#140

Blocks issue #140

  
bug

Defect or regression

  
CI/CD

CI/CD pipeline improvements

  
complexity:low

Low complexity - straightforward implementation

  
complexity:medium

Medium complexity - some unknowns

  
complexity:medium

Medium complexity - some nuance and risk areas

  
config

Configuration files and settings

  
depends-on:#124

Depends on architecture decision issue #124

  
docker

Docker-related tasks

  
docs

Documentation updates and improvements

  
effort:l

L effort estimate - 2-4 weeks (large feature, complex)

  
effort:s

S effort estimate - 2-5 days (small feature, well-defined)

  
effort:xs

XS effort estimate - 1-2 days

  
epic/development

Epic for development phase work

  
lead:complete

Lead engineer review completed

  
needs-decision

Requires human decision before proceeding

  
performance

Performance improvements

  
priority:critical

Must do immediately

  
priority:high

Important for current milestone

  
priority:low

Nice to have

  
priority:medium

Valuable but not urgent

  
security

Security-related concerns

  
spike

Research / exploration

  
story-points:1

Trivial effort

  
story-points:3

Small effort

  
story-points:5

Medium effort

  
story-points:8

Large effort

  
tech-debt

Refactoring / improvement

  
test

Testing-related tasks

  
user-story

Standard user story

  
architect:complete

Architect phase completed

  
complexity:high

High complexity

  
complexity:low

Low complexity

  
complexity:medium

Medium complexity

  
cross-repo

Cross-repository item

  
cross-repo-dev

Cross-repository development

  
dev:in-progress

Development in progress

  
effort:l

Large effort (2-4 weeks)

  
effort:m

Medium effort (1-2 weeks)

  
effort:s

Small effort (2-5 days)

  
effort:xl

Extra large effort (4+ weeks)

  
effort:xs

Extra small effort (1-2 days)

  
epic
analytics
Data analytics of platform data and logs analysis.

  
epic
development
Developing new features, services. front and and back end as well as batch jobs

  
epic
devops
Epic related to CI/CD pipeline, runners, setup and workflow triggers

  
epic
infra
Epic related to infrastructure tasks, configuring hard drives, network equipment, firewalls, anything involving getting hands dirty.

  
epic
observability
Observability stack, uptime, service discovery, network, firewall, processes, resource consumption etc.

  
epic
platform
Related to authentication, authorization, keys, passwords, configs. Updates and upgrades related to platform.

  
epic
product
Issues discussing products and features come over here.

  
lead:complete

Lead/Code review phase completed

  
needs-decision

Requires user decision/selection

  
pipeline-complete

Pipeline completed successfully

  
pipeline-error

Pipeline failed with error

  
pipeline-running

Pipeline is currently running

  
priority
later
To be done but can wait. Generally areas that don't want immediate attention and warrant pre-planning, analysis and/or design

  
priority
next
Not a burning issue but needs to be worked on next. Generally should not be blocked by any issue other than priority::now

  
priority
now
Immediate priority, critical for PROD go-live

  
start-pipeline

Trigger the SDLC pipeline to start

  
status
acceptance
Testing results are good and issue looks good to deploy. It is a pre-deployment sign-off of test results

  
status
blocked
Need to solve another issue before this issue can be picked. The issue is blocked till the blocking issue isn't resolved

  
status
done
Issue deployment successful.

  
status
in progress
Issue has been picked up and someone is working on it.

  
status
in review
The issue has been work on but, a review has been requested, generally good to transition to this if all PRs raised require review or are reviewed.

  
status
in testing
Code review complete and issue is in testing in lower environment. P.S. This means unit tests have already been written.

  
status
ready
Issue does not have any blocker and is ready to be picked.

  
status
refine
Something working already well in PROD but a change that makes life a little more easier, like skip into in netflix. Issues that signify added convenience.

  
status
triage
Issue is requested but not scoped. Need to be added to systematically review and categorize

  
subtask

Subtask issue

  
type
analysis
An issue to perform analysis, exploring deign and implementation decisions/ considerations.

  
type
bug
A bug, needs to be fixed, raised out of an incident.

  
type
hygiene
Features remain the same, makes the platform, faster, better and less-error prone. Makes developer/ system-admin life easier

  
type
mantainence
Primarily version upgrades

  
type
story
Something new, a new feature !

  
user-story

PM-created user story

No Label
architect:complete
blocked-by:#139
blocks:#140
bug
CI/CD
complexity:low
complexity:medium
complexity:medium
config
depends-on:#124
docker
docs
effort:l
effort:s
effort:xs
epic/development
lead:complete
needs-decision
performance
priority:critical
priority:high
priority:low
priority:medium
security
spike
story-points:1
story-points:3
story-points:5
story-points:8
tech-debt
test
user-story
architect:complete
complexity:high
complexity:low
complexity:medium
cross-repo
cross-repo-dev
dev:in-progress
effort:l
effort:m
effort:s
effort:xl
effort:xs
epic
analytics
epic
development
epic
devops
epic
infra
epic
observability
epic
platform
epic
product
lead:complete
needs-decision
pipeline-complete
pipeline-error
pipeline-running
priority
later
priority
next
priority
now
start-pipeline
status
acceptance
status
blocked
status
done
status
in progress
status
in review
status
in testing
status
ready
status
refine
status
triage
subtask
type
analysis
type
bug
type
hygiene
type
mantainence
type
story
user-story
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hithomelabs/CFTunnels#149
No description provided.
Delete Branch "Dave/CFTunnels:ISSUE-139-remove-inputs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?