What
Pull requests in the VS Code repository often have limited visible labeling compared to issues, which makes it harder to quickly understand their scope or impact.
Why
In a large and active repository, being able to quickly identify what a PR affects (area, type of change, scope) helps a lot with triage and reviewer assignment. Right now, that context usually requires manually inspecting the diff.
Proposal
It could be useful to introduce lightweight semantic labeling for pull requests, possibly with some level of automation.
For example, labels could be suggested based on:
- modified folders (e.g. src/vs/workbench, extensions)
- presence of tests
- documentation changes
- number of affected modules
Even simple labels like “workbench”, “extensions”, “docs”, “needs-tests” or “cross-module” could improve visibility and make PRs easier to route.
The idea wouldn’t be to replace human review, but to provide better context earlier in the process.
Thanks for considering it!
What
Pull requests in the VS Code repository often have limited visible labeling compared to issues, which makes it harder to quickly understand their scope or impact.
Why
In a large and active repository, being able to quickly identify what a PR affects (area, type of change, scope) helps a lot with triage and reviewer assignment. Right now, that context usually requires manually inspecting the diff.
Proposal
It could be useful to introduce lightweight semantic labeling for pull requests, possibly with some level of automation.
For example, labels could be suggested based on:
Even simple labels like “workbench”, “extensions”, “docs”, “needs-tests” or “cross-module” could improve visibility and make PRs easier to route.
The idea wouldn’t be to replace human review, but to provide better context earlier in the process.
Thanks for considering it!