-
Notifications
You must be signed in to change notification settings - Fork 66
Add label management instructions and default labels file #41
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ordered list that doesn't render correctly is the only holding back my approval. Everything else is less important.
Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
pyenv all the things
Stop starting over at 1 all the time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for picking all those nits! Great work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is excellent - thanks @hillaryj for a great write-up! 📘
I only can offer two minuscule suggestions...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting this written up. I had some small consistency suggestions and nitpicks. Thanks again!
When you return to the directory in a new shell, remember to: | ||
|
||
```console | ||
pyenv activate github-label-management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you've set up pyenv
as we instruct in our CONTRIBUTING.md
files (cisagov/skeleton-generic's as an example), then this step should not be necessary as long as the correct virtualenv has been set with pyenv local
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be resolved by moving to a skeletonized version in https://github.com/cisagov/github-label-management.
Co-authored-by: dav3r <david.redmin@trio.dhs.gov> Co-authored-by: Nick M. <50747025+mcdonnnj@users.noreply.github.com>
After discussing with @mcdonnnj and for ease of future use, I've created https://github.com/cisagov/github-label-management which will host an updated and genericized version of this tool. I'm incorporating the feedback here into that project and will close this PR once I've gotten that up and running. |
@cisagov/team-ois, can we close this ancient PR? |
Shut 'er down. The repository reference in #41 (comment) has already been deleted as well. |
Closing this ancient PR, as we already have automated label management via a GitHub Action inherited from cisagov/skeleton-generic. |
🗣 Description
Adds a how-to guide for standardizing labels across the organization and a file containing defaults.
Closes cisagov/.github#7
💭 Motivation and Context
Adds documentation for the label-standardization process plus default labels so we can do this again if we need to.
🧪 Testing
Linting passes; labels were successfully applied as per cisagov/.github#7
✅ Checklist
to reflect the changes in this PR.