You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm a contributor from the volcano community. In our community, when a contributor submits a pull request (PR) for the first time, the owner must manually click on the CI to trigger it. Currently, this is a bit troublesome because the owner doesn't have much time to manage these tasks. Instead, we have a volcano-bot using prow. Prow should be able to automatically trigger CI if there is an ok-to-test label. However, we run e2e tests using GitHub workflows. Is there any way to configure the prow trigger plugin so that if there is an ok-to-test label, it can automatically trigger GitHub workflows? Thanks!
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Hi, I'm a contributor from the volcano community. In our community, when a contributor submits a pull request (PR) for the first time, the owner must manually click on the CI to trigger it. Currently, this is a bit troublesome because the owner doesn't have much time to manage these tasks. Instead, we have a volcano-bot using prow. Prow should be able to automatically trigger CI if there is an
ok-to-test
label. However, we run e2e tests using GitHub workflows. Is there any way to configure the prow trigger plugin so that if there is anok-to-test
label, it can automatically trigger GitHub workflows? Thanks!The text was updated successfully, but these errors were encountered: