[PR Workflow] Use more labels for new TypeSpec identification
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Currently we lack of insights on the PRs for newly added product and services. I propose we add similar logic to labeller:
1. `new product`. This gets added whenever new folders are created under the `specification` folder in PR. ie. `specifications/sphere`
2. `new service`. This gets added whenever new **folders** are created:
- directly under `specifications/[product]` eg `specifications/sphere/Sphere.Management`. This is to catch new TypeSpec specs
- directly under `specifications/[product]\data-plane`. This is to catch new data-plane swaggers
- directly under `specifications/[product]\resource-manager` This is to catch new ARM swaggers
With these labels and in conjunction with TypeSpec, we can easily spot TypeSpec adoption violations for the reviewer and BI later.
Contributor guide
Assessment
This issue has not been assessed yet.