github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Workflows started manually with workflow_dispatch runs the main branch workflow for other branches #14122

New Issue
Closed
opened 2025-11-02 11:03:36 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 11:03:36 -06:00
Owner
Copy Link

Originally created by @DesktopMan on GitHub (Feb 11, 2025).

Description

If you start a workflow manually you can choose which branch to run the workflow on. The workflow from the main branch is then executed on the target branch. Shouldn't a manually executed workflow use the workflow file from the branch, and give an error if it doesn't exist?

Steps to reproduce:

  1. Have two branches without workflows: main and test
  2. Add a workflow to the main branch with workflow_dispatch
  3. Manually trigger the workflow, select the test branch

The workflow from the main branch now runs on the test branch, even though the test branch doesn't have any workflows. If the test branch had an updated workflow the old workflow from main would still be used.

Gitea Version

1.23.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Self hosted using official Docker images with Docker Compose.

Database

None

Originally created by @DesktopMan on GitHub (Feb 11, 2025). ### Description If you start a workflow manually you can choose which branch to run the workflow on. The workflow from the main branch is then executed on the target branch. Shouldn't a manually executed workflow use the workflow file from the branch, and give an error if it doesn't exist? Steps to reproduce: 1. Have two branches without workflows: main and test 2. Add a workflow to the main branch with workflow_dispatch 3. Manually trigger the workflow, select the test branch The workflow from the main branch now runs on the test branch, even though the test branch doesn't have any workflows. If the test branch had an updated workflow the old workflow from main would still be used. ### Gitea Version 1.23.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Self hosted using official Docker images with Docker Compose. ### Database None
GiteaMirror added the type/bugissue/needs-feedback labels 2025-11-02 11:03:36 -06:00
GiteaMirror commented 2025-11-02 11:03:37 -06:00
Author
Owner
Copy Link

@austinankur commented on GitHub (Feb 12, 2025):

I can confirm this bug

@austinankur commented on GitHub (Feb 12, 2025): I can confirm this bug
GiteaMirror commented 2025-11-02 11:03:37 -06:00
Author
Owner
Copy Link

@Zettat123 commented on GitHub (Feb 13, 2025):

I think this issue has been fixed by

@Zettat123 commented on GitHub (Feb 13, 2025): I think this issue has been fixed by - #33098
GiteaMirror commented 2025-11-02 11:03:37 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Mar 16, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Mar 16, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14122
Delete Branch "%!s()"

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?