Prow is a Kubernetes based CI/CD system developed to serve the Kubernetes community. This repository contains Prow source code and Hugo sources for Prow documentation site.
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!
In response to [this](https://github.com/kubernetes-sigs/prow/issues/284#issuecomment-2383005501):
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) 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!