kubernetes: `vendor/modules.txt` is hot for conflicts and approval bottleneck
Any package change in a staging repository has to include its new packages in vendor/modules.txt which creates a bottleneck for conflicts and approval.
Can we split the file so that various parts can be owned by different groups of people?
/assign @liggitt
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (12 by maintainers)
the file is generated by
go mod vendor, so nowe could expand the set of approvers just for that file that to be dep-approvers OR staging approvers, seeing as that file is autogenerated anyhow and actual vendor changes would include other files, but not without the test-infra fix.