-
Notifications
You must be signed in to change notification settings - Fork 17
Add a workflow to label issues #43
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
base: main
Are you sure you want to change the base?
Conversation
This ensures new and reopened issues are labeled sig/multicluster, which makes them show up in our triage filter. Labels could also be added using issue templates, but users can always choose to create an issue using a blank template and thereby skip the automatic labeling. Using a workflow ensures all issues are caught. Signed-off-by: Stephen Kitt <[email protected]>
✅ Deploy Preview for kubernetes-sig-multicluster ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: skitt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
/remove-lifecycle stale /cc @lauralorenz |
This ensures new and reopened issues are labeled sig/multicluster, which makes them show up in our triage filter.
Labels could also be added using issue templates, but users can always choose to create an issue using a blank template and thereby skip the automatic labeling. Using a workflow ensures all issues are caught.