The Run workflow button is missing for a GitHub Actions workflow
No Run workflow button above the list of workflow runsShort answer
The Run workflow button appears only when the workflow file has the workflow_dispatch trigger and sits on the default branch, and running it needs write access to the repository. Add the trigger, merge the file to the default branch, or ask for write access.
Fix it fast
1Find out which cause you have
Open the workflow file on the default branch (not your feature branch) and look at its on: block.
grep -n -A6 "^on:" .github/workflows/*.yml2Match what you see, then jump to its fix
- 1
The workflow runs on push or pull_request but shows no button.The workflow has no workflow_dispatch triggerFix - 2
workflow_dispatch is in your branch's file, but not in the file on the default branch.The trigger exists only on a feature branchFix - 3
Others see the button, you do not.Your account has no write access to the repositoryFix
- 1
What does the error look like?
No Run workflow button above the list of workflow runs
Cause 1 of 3
The workflow has no workflow_dispatch trigger
1Check
The button is shown only if the workflow file uses the workflow_dispatch event.
grep -n "workflow_dispatch" .github/workflows/*.yml2Fix
Add workflow_dispatch to the on: block, with optional inputs.
on:
push:
branches: [main]
workflow_dispatch:
inputs:
logLevel:
description: 'Log level'
required: true
default: 'warning'
type: choice
options:
- info
- warning
- debug3Verify
After the change is on the default branch, the Run workflow button appears.
gh workflow run build.yml -f logLevel=infoConfirmed by docs.github.com
Cause 2 of 3
The trigger exists only on a feature branch
1Check
The workflow must be in the default branch to trigger workflow_dispatch, and the event receives events only when the file is on the default branch.
git show origin/main:.github/workflows/build.yml | grep -n workflow_dispatch2Fix
Merge the change into the default branch. After that you can pick any branch in the Branch dropdown, or pass one with --ref.
gh workflow run build.yml --ref my-feature-branch3Verify
The button shows and the run starts on the chosen branch.
gh run list --workflow build.yml --limit 3Confirmed by docs.github.com
Cause 3 of 3
Your account has no write access to the repository
1Check
Write access to the repository is required to run a workflow manually.
# ask a repository admin which role your account has2Fix
Ask an owner for write access, or have them run the workflow.
# role change by a repository admin3Verify
After the role changes, reload the Actions tab: the button shows.
gh workflow run build.ymlConfirmed by docs.github.com
How do I stop it coming back?
- Add workflow_dispatch to utility and deploy workflows when you create them.
- Merge workflow changes to the default branch before testing the button.
- Keep a short list of who has write access to repositories with deploy workflows.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Servers
Docker push to Artifact Registry fails from GitHub Actions with a permission error
Permission 'artifactregistry.repositories.uploadArtifacts' denied on resource
The identity your workflow authenticates as lacks the permission artifactregistry.repositories.uploadArtifacts on the target repository.
4 causes, each with a fixServers
docker pull or push to ghcr.io fails with 'denied'
Error response from daemon: denied
ghcr.io refuses a pull or push when Docker is not logged in, when the token lacks the package scope, or when the workflow's GITHUB_TOKEN has no packages permission or no access to that package.
4 causes, each with a fixServers
git says it could not read Username for https://github.com in a build or CI job
fatal: could not read Username for 'https://github.com': No such device or address
Git asked for HTTPS credentials and there was no terminal to ask on, so it gave up.
3 causes, each with a fixServers
upload-artifact fails because the artifact storage quota is full
Create Artifact Container failed: Artifact storage quota has been hit. Unable to upload any new artifacts
Uploads fail when your account's shared artifact storage is used up.
3 causes, each with a fixServers
configure-aws-credentials says no OpenID Connect provider exists for GitHub
No OpenIDConnect provider found in your account for https://token.actions.githubusercontent.com
AWS has no IAM identity provider for GitHub's token issuer in the account that holds the role.
3 causes, each with a fixServers
A local composite action in GitHub Actions cannot be found
The action folder is in the repository but the runner reports that its action.yml cannot be found
A local action is read from the checked-out repository.
3 causes, each with a fix