[P0] Import existing data and then validate existing codeowners information into ADO work items as a new codeowner data source of truth
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
o If SDK codeowner information must persist in the codeowners file, it should be sync’d from the new source of truth
o The centralized source of truth must be the only place where valid codeowner data is maintained. Any updates should flow directly into CODEOWNERS files, and we’ll avoid supporting overrides or alternate data entry points.
o Replace existing GitHub codeowners information in codeowners files from the new centralized source of truth i.e., [DJ6.1]we should “render” the relevant CODEOWNERS file entries from the source data.
o https://github.com/Azure/azure-sdk-for-js
o https://github.com/Azure/azure-sdk-for-python
o https://github.com/Azure/azure-sdk-for-java
o https://github.com/Azure/azure-sdk-for-net
o https://github.com/Azure/azure-sdk-for-rust
o https://github.com/Azure/azure-sdk-for-cpp
o https://github.com/Azure/azure-sdk-for-go
o https://github.com/Azure/azure-rest-api-specs
o Whatever data source we use will need the flexibility for service teams to assign different owners for different repos/languages from the same place or page. Fo
Contributor guide
Assessment
This issue has not been assessed yet.