Open saschagrunert opened 10 months ago
Removing the point "Automatically validate cherry-picks across different release branches (we usually apply them in batches)" because of https://github.com/kubernetes/community/issues/7634
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
This is the tracking issue for possible improvements to the
cherry-pick-approved
prow plugin: https://github.com/kubernetes/test-infra/tree/9d444ae/prow/plugins/cherrypickapprovedFollow-up on: https://github.com/kubernetes/sig-release/issues/2083 Mailing list thread: https://groups.google.com/a/kubernetes.io/g/dev/c/U1Na5ce6Mck
/kind feature /priority important-longterm