Closed samuelweiler closed 2 years ago
Similarly, why does https://github.com/w3cping/tracking-issues/issues/233 (an issue pointing to the TAG design reviews repo) get a label whereas https://github.com/w3cping/tracking-issues/issues/239 does not?
Here's another one: https://github.com/w3cping/tracking-issues/issues/245
When a repository is associated with multiple shortnames, I usually have to go and add the label manually, because the tool declines to pick one. So, I go and add those labels from time to time (which explains why I'm the one adding the label and not w3cbot).
For https://github.com/w3cping/tracking-issues/issues/233 and https://github.com/w3cping/tracking-issues/issues/239 , the tool isn't intelligent enough to know which spec is getting reviewed in the TAG design repo.
For https://github.com/w3cping/tracking-issues/issues/245 , https://github.com/w3c/personalization-semantics contains more than one document and the tool doesn't know how to differentiate.
The only exception is the csswg-drafts repository where, using the CSS convention in the issue title, the tool attempts to set the proper label.
(closing for now)
Why does https://github.com/w3cping/tracking-issues/issues/242 not have a shortname label?