-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Enable Prow plugins for etcd PRs #18110
Comments
Sounds good to me. |
Thanks for proposing this @ArkaSaha30. Enabling the cherry pick plugin makes sense to me, please feel free to raise a pr if you have capacity 🙏🏻 |
/assign |
This commit will add cherrypicker external plugin for etcd-io/etcd repo. Issue ref: etcd-io/etcd#18110 Signed-off-by: arkas1 <[email protected]>
This commit will add cherrypicker external plugin for etcd-io/etcd repo. Issue ref: etcd-io/etcd#18110 Signed-off-by: arkas1 <[email protected]>
This commit will add cherrypicker external plugin for etcd-io/etcd repo. Issue ref: etcd-io/etcd#18110 Signed-off-by: ArkaSaha30 <[email protected]>
Hi @ArkaSaha30 - We raised this at sig-etcd triage meeting, are there any other plugins you suggest we enable or can we close this now? |
Based on kubernetes/k8s.io#6102 (comment), do we also want to enable tide, lgtm, and approve? |
Yes! Along with these we can also add 'size' which will label the PRs based on how lengthy it is. WDYT @jmhbnz ? |
I am not confident we are ready as a project for I am happy to enable the pr sizing plugin as that is very low risk. |
Discussed during sig-etcd triage meeting, the next major step for this issue is to enable This will be a significant change for
|
What would you like to be added?
Plugin enablement for etcd in test-infra.
Suggested plugins to be added:
Why is this needed?
There are useful Prow plugins that etcd can leverage to minimize manual efforts. One of them is the cherrypicker plugin, which can backport any PR to a specific branch with just a
/cherry-pick <branch_name>
comment on the PR.Example: containerd/containerd#10257 (comment)
The text was updated successfully, but these errors were encountered: