how to trigger workflow_dispatch event which not in default branch

[minesunny]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

the default workflows show that the defualt branch have, if I create a new workflow on the new branch, it doesn't show that and I cloudn't tragger that

[VictorMoni]

Hi @minesunny

By default, GitHub’s Actions tab only lists workflows from the default branch, so if you create a workflow in another branch, it won’t appear there unless you switch branches.

To trigger a workflow_dispatch on a non-default branch, you have two main options:

1. Trigger from the Actions UI

• Go to the Actions tab.

• Use the branch selector at the top-left to switch to the branch containing the workflow.

• Select the workflow and click Run workflow, choosing the same branch.

2. Trigger via GitHub API

• Call the workflow_dispatch endpoint with:

{
  "ref": "branch-name",
  "inputs": { ... }
}

• This lets you run the workflow even if it’s not on the default branch.

[minesunny]

Hi @minesunny

By default, GitHub’s Actions tab only lists workflows from the default branch, so if you create a workflow in another branch, it won’t appear there unless you switch branches.

To trigger a workflow_dispatch on a non-default branch, you have two main options:

1. Trigger from the Actions UI

• Go to the Actions tab.
• Use the branch selector at the top-left to switch to the branch containing the workflow.
• Select the workflow and click Run workflow, choosing the same branch.

2. Trigger via GitHub API

• Call the workflow_dispatch endpoint with:

{
  "ref": "branch-name",
  "inputs": { ... }
}

• This lets you run the workflow even if it’s not on the default branch.

I don't find the branch selector

[VictorMoni]

You can trigger workflow_dispatch from a non-default branch, but a few details matter.

1) Check the basics

• The workflow file exists on that branch at .github/workflows/.yml.

• It contains on: workflow_dispatch (optionally with inputs):

name: build
on:
  workflow_dispatch:
    inputs:
      env:
        description: Environment
        required: false
        default: dev

• You have Write access to the repo (otherwise the “Run workflow” button won’t appear).

2) Trigger from the UI

The branch selector is not on the “All workflows” list. You’ll see it only on the page for a specific workflow:

1. Go to Actions → click the workflow’s name (left sidebar).

2. On that workflow page, click Run workflow (top-right).

3. In the dropdown, use “Use workflow from” to pick your branch (you can type to search).

4. Fill any inputs and click Run workflow.

If you still don’t see the branch: the workflow file probably isn’t present on that branch, or the YAML has a syntax error so GitHub didn’t register it.

3) Trigger with CLI (easy)

# Install GitHub CLI and auth first: gh auth login
gh workflow run .github/workflows/<name>.yml \
  --ref feature/my-branch \
  -f env=dev

4) Trigger with REST API

curl -X POST \
  -H "Authorization: Bearer <TOKEN_WITH_WORKFLOW_SCOPE>" \
  -H "Accept: application/vnd.github+json" \
  https://api.github.com/repos/<owner>/<repo>/actions/workflows/<name>.yml/dispatches \
  -d '{"ref":"feature/my-branch","inputs":{"env":"dev"}}'

5) Common gotchas

• Forks: maintainers must enable workflows; otherwise “Run workflow” is hidden.

• Repo settings: Actions might be restricted by org policy.

• YAML name mismatch: You can reference the workflow by file name or workflow ID in the API/CLI—make sure it matches.

• Conditional guards: An if: at job/workflow level could prevent runs on certain branches.

If you want, share your repo/branch name and the workflow file path, and I’ll point out exactly what’s missing.

[minesunny]

why it still find the workflow from the default branch

[hellmelt]

If the workflow never has run, it won't appear in the list of workflows. So there is no way to select it and get to the "Run Workflow" button.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬