-
Notifications
You must be signed in to change notification settings - Fork 59.9k
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
documentation on on.workflow_dispatch
is not correct/complete
#34884
Comments
on.workflow_dispatch
is not correcton.workflow_dispatch
is not correct/complete
@tomsit-ionos Thank you very much for raising an issue! ✨ While we appreciate the method you've shared to run WFs via the For that reason, we are unable to add this to our docs. We still thank you for your willingness to contribute 🙇 If you're looking for issues to pick up, take a look at our help wanted section to find open issues you can work on 💛 |
hm, that is unfortunate. |
This question would best be handled by our wonderful support team - please feel free to reach out to them 💛 |
@tomsit-ionos Thank you! We're reviewing this now, and will provide an update after 👍 |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#repository_dispatch
Note that this text is defined on 1 place (
{% data reusables.actions.workflow-dispatch %}
) and used in several places.It might be that it is correct in some use cases.
What part(s) of the article would you like to see updated?
it is possible to run WFs via
workflow-dispatch
event on branches other than the default (thru the API, maybe not UI)there are some ramifications though
GH CLI
by also adding anon.push
while on a feature branchsee
Additional information
cli/cli#5268
The text was updated successfully, but these errors were encountered: