Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DesktopMan opened this issue Feb 11, 2025 · 3 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug

Comments

@DesktopMan
Copy link

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

@austinankur
Copy link

I can confirm this bug

@Zettat123
Copy link
Contributor

I think this issue has been fixed by

@lunny lunny added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Feb 14, 2025
@GiteaBot
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug
Projects
None yet
Development

No branches or pull requests

5 participants