-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
cherrypick plugin doesn't response to all commands in a github comment #29666
Comments
/sig testing |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/lifecycle frozen |
cherrypick is now at https://github.com/kubernetes-sigs/prow/tree/main/cmd/external-plugins/cherrypicker unfortunately github cannot move issues across repos, but if you're still interested, please re-file against the prow issue tracker, I'm working on closing out prow issues here |
What happened:
cherry-pick plugin didn't detect multiple uses of /cherry-pick command in the same message
ie. from knative/serving#14028 (comment)
What you expected to happen:
It would create two cherry pick PRs
How to reproduce it (as minimally and precisely as possible):
Please provide links to example occurrences, if any:
Anything else we need to know?:
This was fixed but seems to have regressed
#21684
#21714
Knative is using
From: https://github.com/knative/infra/blob/main/prow/cluster/control-plane/500-cherrypicker.yaml
The text was updated successfully, but these errors were encountered: