-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Subprojects in sigs.yaml will be instantly out of date #1913
Comments
/sig contributor-experience yeah, there are some updates that are going to have to be made to the generator to accommodate the new structures in https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/area github-management Yeah I agree until there's a single source of truth this is going to be perpetually stale. It started in sigs.yaml because it's easier to try and change everything in one place while getting started. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/kind bug |
/assign |
/remove-priority important-soon |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale Due to important long term label. |
/committee steering |
/assign |
see new tool for ensuring urls are still valid ( #4125 (comment) ) |
related #6307 |
with the annual report checks and the new tool above that dims linked, @lavalamp do you think we are in a better place now and ok to close this? |
/assign @palnabarun |
Anytime anyone moves a directory, the entry in sigs.yaml will suddenly be wrong.
Wouldn't it make more sense for OWNERS files to instead declare the owning sig and subproject, and then we generate sigs.yaml from that?
The text was updated successfully, but these errors were encountered: