-
Notifications
You must be signed in to change notification settings - Fork 39
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
[pre-]populating with GitHub labels #69
Comments
some thoughts:
|
I'm not saying groups should do this (it's cumbersome) but, for the record, @sandhawke documented a way to import labels programmatically, and suggested an initial set of labels of his own.
There was more or less agreement about merging Sandro's labels with the ones already in this repo. Anyway, the set here has been extended and redefined in the meantime, so I propose we consider the suggested labels good enough, and forget about them until we get significant feedback after some time. Anyway, +1 to @dontcallmedom's suggestion about doing this from the Repo Manager at some point. |
@tripu should this be co-assigned to you if you're looking at ash-nazg? |
There is no way to import labels to a [new] repo. Instead, one has to add them by hand.
This would allow WGs to reuse the same labels and to provide on top of that a consistent tool that would output a disposition of comments.
Labels are also listed here
https://w3c.github.io/issue-metadata.html
The text was updated successfully, but these errors were encountered: