I have the same problem as well.
I try to setup workflow_dispatch event to launch several workflows from GitHub UI.
My final goal to setup it for release-branch.yml, rust-nightly.yml and rust-release.yml workflows in https://github.com/intellij-rust/intellij-rust repository.
To avoid unexpected errors in original repo I tried to make the corresponding changes in my own fork (Enable local and third party Actions for this repository option in Actions permissions settings is enabled)
The current result:
The corresponding UI is shown only for release-branch.yml workflow
item for rust-nightly.yml workflow disappeared at all. Note, it happened after workflow file renaming (and it’s probably the separate bug but anyway). Before this renaming, result was the same as for rust-release.yml workflow.
@cschleiden Managed to fix my issue where I was not seeing the “Run workflow” button in my workflow_dispatch event workflows. This might be an issue with the parser you guys have for these files. I have 3 different workflows files (one for pull_request events, one for push events and one for workflow_dispatch events) where the same workflow name is used in these workflows files. I see no issue with having two (for pull_request and for push events) different workflow files with the same name. The workflow file for the workflow_dispatch event had the same name and I guess this caused to not see the ‘Run workflow’ button. After given a different name to the workflow_dispatch event workflow I see the ‘Run workflow’ button. I hope I explained myself clearly. Let me know if you are interested on having more info. Thanks.
You can see the env variable is not set in this run.
I can’t reproduce the parsing error from my private repo even by copy pasting the file contents. Not sure what’s up there. I’m adding back my real workflow to my private repo piece by piece to see if I can pinpoint where it starts failing to parse
Edit: Okay, I got it to happen again. I pasted in my intended input definition, committed and pushed, then my action started failing to parse again with " No event triggers defined in on``"
I uploaded the patch that brought the error back.
I can see a weird character in the patch, but I don’t see it in Notepad++ with all symbols turned on. It could be my editor (JetBrains Rider) inserting the characters but this is pretty confusing.
I appreciate all the work the team has done on GitHub actions. I’m not trying to complain too much. It’s just a bit frustrating to hit these kinds of walls is all, but it’s all in the life of a coder. Maybe I should try to use a different editor for now but I can’t even see this character.
I am facing a similar issue with private repository
In order to make workflow action visible, I have to get it triggered once by the push or something automatic, then revert the commit for auto triggers and have only manual triggers, then only the button appears to trigger it manually.
Let me know if I should provide any specific details. The branch is default branch, but to reproduce it, if any yaml file has only workflow action in private repo it just doesn’t appear.
This is the way I am using it.
description: 'Environment to deploy on'
description: 'Terraform Action to perform'
description: 'Extra Args for tf command'
@cschleiden just FYI we had this bug too and had to rename the file.
In our case, we force pushed the git history back in time to where the file no longer existed, then merged a PR to add it back in. After this happened, the workflow never appeared in the UI (even after I forked the repo!) It was only after renaming the file it started showing up.