ci: add workflow_dispatch#1387
Conversation
afdf43a to
b0698b0
Compare
|
ping @jpmcb |
I'm not sure why we need this? Why would a maintainer need to manually trigger the github actions? |
The CI workflow depends on some external dependencies which might change without modifications in the codebase of this repository. Currently, the only solution to have those tested is to rerun an existing workflow, or to push/ammend a "dummy" branch. Having this option avoids that. Moreover, having this added to the workflow in the default branch will allow users to use the feature in their forks. Hence, even though manually triggering CI might not be used by maintainers of this repo, it can be useful for contributors. |
581a01a to
f7b7285
Compare
|
Can we please have this one-liner merged? |
a91c7ad to
fcb2303
Compare
de4f5c1 to
51c4abc
Compare
e56930d to
e4e043f
Compare
* main: (39 commits) Add '--version' flag to Help output (spf13#1707) Expose ValidateRequiredFlags and ValidateFlagGroups (spf13#1760) Document option to hide the default completion cmd (spf13#1779) ci: add workflow_dispatch (spf13#1387) add missing license headers (spf13#1809) ci: use action/setup-go's cache (spf13#1783) Adjustments to documentation (spf13#1656) Rename Powershell completion tests (spf13#1803) Support for case-insensitive command names (spf13#1802) Deprecate ExactValidArgs() and test combinations of args validators (spf13#1643) Use correct stale action `exempt-` yaml keys (spf13#1800) With go 1.18, we must use go install for a binary (spf13#1726) Clarify SetContext documentation (spf13#1748) ci: test on Golang 1.19 (spf13#1782) fix: show flags that shadow parent persistent flag in child help (spf13#1776) Update gopkg.in/yaml.v2 to gopkg.in/yaml.v3 (spf13#1766) fix(bash-v2): activeHelp length check syntax (spf13#1762) fix: correct command path in see_also for YAML doc (spf13#1771) build(deps): bump github.com/inconshreveable/mousetrap (spf13#1774) docs: add zitadel to the list (spf13#1772) ...
The workflow dispatch event allows maintainers or forkers to trigger CI runs either through the web GUI or through the API. See https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch.