-
Notifications
You must be signed in to change notification settings - Fork 1
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
Standardize labels #2
Comments
sure, why not (watching now) |
FWIW it appears repo-utils/org-labels#30 is needed to make org-labels run. At least that's what @skddc claims |
It's actually enough to manually edit the OAuth scope for the token created by the CLI auth, in one's user settings on GitHub. Needs to include "repo". |
I suggest closing this; labels have been working fine the way they are and I don't see as much value in standardising them any more. |
i feel the same way. |
Rather than manually creating labels on each project, I'd really like to have these standardized (eg:
needs tests
,glitch
,bug
, etc) for all of pimutils.repo-utils/org-labels might help us maintain this (and copy labels to todoman, which currently only has one or two), though me need to make sure we actually standardize them on every repo first.
How does everyone feel about this?
cc @untitaker @geier (I think we should all
watch
this repo).The text was updated successfully, but these errors were encountered: