Compute multi-spec repositories automatically #660
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The list of multi-spec repositories was hardcoded and slightly outdated. The update now computes that list automatically from the data present in the results of the crawl (which comes from browser-specs). Compared to the previous list, the new logic misses
w3c/woff
because it voluntarily skips repositories that contain multiple versions of the same spec to avoid false positives. It adds:https://github.com/httpwg/http-extensions
https://github.com/immersive-web/real-world-geometry https://github.com/w3c/aria
https://github.com/w3c/encrypted-media
https://github.com/w3c/gamepad
https://github.com/w3c/reporting
https://github.com/w3c/webcodecs
https://github.com/WebAssembly/threads
https://github.com/WebBluetoothCG/web-bluetooth
https://github.com/WICG/nav-speculation
https://github.com/WICG/shape-detection-api
https://github.com/WICG/WebApiDevice
Some of them contain one "main" spec and side specs that we will probably ignore for some time, but then it does not hurt to prefix issues with the spec's shortname in such cases, even if the targeted spec is somewhat obvious.