-
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
Add kind/kep label #9437
Add kind/kep label #9437
Conversation
@cblecker --
|
48b42d3
to
05b3032
Compare
Hey @k8s-ci-robot, promise I'm actually running the script. See?
/test pull-test-infra-verify-labels |
d6ce43d
to
185e531
Compare
(Fun fact: the |
/uncc I'm happy if cblecker is happy |
As much as I cringe to see another Ideally this would be obviated by moving keps to their own repo, so you could just query for |
label_sync/labels.yaml
Outdated
kubernetes/community: | ||
labels: | ||
- color: cc99ff | ||
description: Categorizes issue or PR as related to a KEP. |
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.
That said, I don't see mention of the reason or need for kind/kep
in the meta-kep proposal. This description is too vague. ie: what I do not want to see is PR's that implement a KEP being labeled as kind/kep
, that is not a kind of work.
I was assuming it was solely to be able to query what PR's are KEPs as an interim to transitioning them into kubernetes/keps. Which now that I think of it, does seem like an appropriate use for an area/keps
label, to signify something is going to be done with these as part of that effort.
tl;dr I just talked myself back into wanting to block this. Why do you need this label? |
What are your thoughts on keps having their own repo? @cblecker @justaugustus ? This sounds nice to me. IMO we should try more focused repos and less heavily overloaded ones. It would also help and with interested parties (reviewers?) trying to subscribe to KEPs without signing up to monitor all community changes. |
+1 to a |
I'd like to see KEP-1a get to implementable before moving on this |
@spiffxp -- Ideally, I'd love to see this go in first, so I can release kubernetes/community#2677. |
73351ce
to
142992e
Compare
142992e
to
4cc0bf0
Compare
/retest |
The
/override pull-test-infra-verify-labels |
@justaugustus: justaugustus unauthorized: /override is restricted to repo administrators 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. |
4cc0bf0
to
43565a9
Compare
Label CSS is fixed in #9633 |
Signed-off-by: Stephen Augustus <[email protected]>
43565a9
to
f92916f
Compare
With KEP-1a merged, this is ready to go as well. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justaugustus, spiffxp 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 |
/hold cancel |
@justaugustus: Updated the
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. |
/sig pm architecture
rel:
Signed-off-by: Stephen Augustus [email protected]