lhotari opened a new issue, #17567: URL: https://github.com/apache/pulsar/issues/17567
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation We have many active branches and many commits are pushed to these branches. master branch gets commits by merging PRs and in most cases, commits are pushed by cherry-picking commits from master branch to maintenance branches (branch-2.11, branch-2.10, branch-2.9, branch-2.8 and branch-2.7). In most cases, nobody pays attention to the results of individual builds for commits pushed to maintenance branches. Therefore, it would be a way to save CI resources if CI builds are only available upon request or in a scheduled manner. ### Solution GitHub Actions has a feature for manually triggering the workflow. Documentation: https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#defining-inputs-for-manually-triggered-workflows workflow_dispatch is the event type. Docs for workflow_dispatch https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch The GitHub UI lets the user choose the branch. The minimum way to add support for manual triggering is adding `on: workflow_dispatch` to the workflow. ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
