-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Remove auto-labelling for clusterctl #8990
🌱 Remove auto-labelling for clusterctl #8990
Conversation
Signed-off-by: killianmuldoon <kmuldoon@vmware.com>
/area release |
/lgtm |
LGTM label has been added. Git tree hash: cf3bd26b65b816d5ed16c5a4640b1e49c651aea2
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/remove-area clusterctl |
/cherry-pick release-1.5 |
@killianmuldoon: new pull request created: #9659 In response to this:
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/test-infra repository. |
This behaviour of automatically adding a code area based on the OWNERs file is not a great solution as it exists for release notes.
We should revisit automating these labels in a more holistic way, but for now this should be removed.