Managing GitHub Labels
I was on a sprint planning call last week where it felt like we spent way too much time getting the labels in our various repos straightened out.
After a little Googling I found various scripts that use the GitHub API to manage labels. But nothing that seemed easy enough. So… I pulled together my own repo of scripts – atsign-company/labels, which we have now open sourced.
When a label is added to that repo it fires a GitHub Action that pushes the new label to all the repos listed in a config file (in our case atsign-foundation.yaml for our open source repos).
Thanks to Olivier Jacques for pointing me to the ability to start an Action from a labels event, and to the DXC DevOps Dojo team for having a nice labeling script as part of the Welcome module.
Filed under: howto | 2 Comments
Tags: action, github, labels, open source, python, script
Subscribe
Recent Comments
Tim Coote on Ross Anderson RIP iain on Skiing in Espace Killy (Val… Chris Swan on Getting more from a British Ga… Murray Cowell on Getting more from a British Ga… JL on AI MacGuffin 
Pinboard.in bookmarks- Open Source Security (OpenSSF) and OpenJS Foundations Issue Alert for Social Engineering Takeovers of Open Source Projects
- AI isn't useless. But is it worth it?
- Pluralistic: The true post-cyberpunk hero is a noir forensic accountant
- Subaru battery drain due to missing 3G network
- Paying maintainers: the HOWTO
- SARS-CoV-2 airborne infection probability estimated by using indoor carbon dioxide | Environmental Science and Pollution Research
- An unbiased evaluation of environment management and packaging tools
- Computer says no: British judge refuses to cancel divorce resulting from computer mistake
- Philosophy Museum
- Royal Navy offer must improve to attract and retain staff – you can't motivate an empty chair
Chris Swan's Weblog 
This looks great Chris! At https://github.com/resonatecoop we desperately need a sort out, and this looks like it will be very handy across all our platform repos. We’re also looking to set up a ‘project of projects’ to make a nice roadmap with milestones across all repos and pick out key project dependencies… 😉
I’ve started using an ‘archetype’ repo which has templates for README, code of conduct, CONTRIBUTING, issues and PRs.
For new stuff I could just use a template repository, and I’ll probably do that too based on ‘archetype’, but for now the focus is on bringing existing repos up to scratch and knowing what good looks like.