GitHub action to update interop proposals with web-features-explorer data #978
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgraham
reviewed
Jul 17, 2025
| } else if (feature.status && feature.status.baseline === "low") { | ||
| return "Newly Available"; | ||
| } | ||
| return "Limited Availability"; |
There was a problem hiding this comment.
There might also be totally unimplemented features, right?
There was a problem hiding this comment.
Yes, but Limited Availability currently encompasses them too.
foolip
reviewed
Jul 24, 2025
| str += getUseCounterAsMarkdown(feature); | ||
| str += getSurveysAsMarkdown(feature); | ||
| str += getPreviousInteropsAsMarkdown(feature); | ||
| str += getWPTLinkAsMarkdown(feature); |
There was a problem hiding this comment.
Do you have a issue where the WPT link is added and working? It seems like everything is there in captainbrosset/interop-proposals-bot#1 for it to be added, but it's not. Maybe there's a bug here?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a PR for a proposal I made on a recent interop team meeting, also based on a discussion with @jgraham, and thanks to feedback I got from multiple people at that meeting.
The PR consists of a GitHub action which runs when a new issue is created, and when an existing issue is edited.
The action runs a NodeJS script (in the new
/scripts/folder), which reads the issue body and attempts to find web-features that correspond to various URLs found in the body.This can obviously be improved, but I wanted to open this PR early for a first round of feedback/review.
I don't know of a way to test GitHub actions without pushing changes to the main branch of a repo though, so I tested this on my own repo here: https://github.com/captainbrosset/interop-proposals-bot, and you can see a few issues which I experimented with: https://github.com/captainbrosset/interop-proposals-bot/issues
To test this further, feel free to create more issues on my repo.
So far, I mainly tested this in "happy path" scenarios, for example with a spec URL that actually matched a web-features entry. However, there are many focus area proposals from last year which don't return any web-features because they either don't have data we can use, or because the spec URL differs slightly.
So, one thing we should do here is test this with a bigger variety of existing issues and improve the web-features detection code accordingly.