-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a bot file issue for MDN when the "impacts documentation" label is added #111
Comments
It wasn't entirely clear to me that @chrisdavidmills et al wanted this kind of thing. |
It might be good for the moment to just have it send me an email every time the label is added. But I'll discuss it in our team meeting next week. |
The @whatwg/documentation team has since been created. For how teams are used in the WHATWG github org, https://github.com/whatwg/meta/blob/master/GITHUB-TEAMS.md But the gist of it is, anybody who sees an issue or PR as affecting documentation can mention the @whatwg/documentation team in a comment, and everybody in that team will get a notification. So I’m gonna close this issue out as being resolved by that (but @zcorpan if there’s still more you reckon we ought to be for this, feel free to reopen it). |
I still like this idea, although the bot could file the issue only when a PR with the label is merged (or an issue with the label is closed by a merged PR), so as to not prematurely ask to document things that are not ready. An alternative we discussed in Matrix today was to use the "impacts documentation" label on closed issues as the source of truth, however I think it's less natural to track issues that way as compared to open issues on the relevant documentation repo directly. |
Issues are now filed as part of PRs that change standards. Automating that could be interesting still I suppose. |
cc @sideshowbarker
The text was updated successfully, but these errors were encountered: