Missing workflow_dispatch at the Action tab

I was doing some tests with the workflow_dispatch and it was working great until I did a force push into master (it’s a private and not used by others repository) to move the changes from master to a pull request.
One of those changes was the workflow_dispatch. After I did this the workflow doesn’t shows up anymore at the Action tab.

GitHub got into an invalid state? What I can do to solve this problem?

I tried to delete the file and then create using the graphic interface, but I got the same result.

1 Like

The workflow file must be committed in the default branch (master/main) if you want to use the workflow_dispatch event. Is it still present there or only on a feature branch?

1 Like

Yes, the file is at the default branch and still doesn’t show to me on the actions tab. It’s not the first time this happens to me. Looks like GitHub get into an invalid state and after that, I can’t use the manual workflow at the repository anymore.

It’s not like I can’t see the Run workflow button, I can’t see the whole workflow. The other workflows that I have at the repository are there and working fine.

It’s a bug with GitHub, I just confirmed. I changed the name of the files and the name of the workflow and now it’s showing for me.

1 Like

Thanks. I had the same problem with not displaying the workflow button on the page. After changing the file name, it works.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        renamed:    .github/workflows/develop.yml -> .github/workflows/build.yml

May we get a notification, when this bug is fixed? It’s quite annoying. I faced it as well.

This has been fixed, if you are still seeing a problem, please let us know where.

Hey @andymckay !
It happened just today in my private repository. I have pushed there a copy of the public repository with already existing workflows. The workflow that was supposed to be triggered manually only wasn’t detected by Github and therefore didn’t show up in Actions tab. So, I wasn’t able to trigger it. Neither via UI, nor via REST API. I had to rename a workflow file in master to make Github notice that workflow and let me run it eventually. Renaming a workflow in a branch didn’t help.

Thank you, I’ll file an issue internally and the team will take a look.

1 Like

I was able to reproduce what you describe. I didn’t need to rename the file, but instead just added a comment to the file and noticed the workflow was created.

Still couldn’t get it to work in a private clone of a private repository. I’ve tried adding a comment as @lupine86 suggested but the button still didn’t appear.

It is not working for me either! no button for the workflow is being shown.