Add automation to ensure new fields are added to extended release channel
Open
community/help wanted
kind/enhancement
- Dominant language
- Go
- Stars
- 519
- Forks
- 612
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 23
Description
When new fields are added to v1 resources, they should go to the extended channel (via the field comment). We should have automation to enforce this
Contributor guide
Assessment
This issue has not been assessed yet.