Skip to content
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

feat: define github issue labels as code #30

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NuclearRedeye
Copy link
Contributor

Current WIP to define a set of core issue labels and have each change automatically update the labels in a defined list of repos.

@NuclearRedeye NuclearRedeye force-pushed the wip/github-issue-labels branch from a8a9b24 to 9640e84 Compare March 21, 2021 21:50
@lsh-0
Copy link
Contributor

lsh-0 commented Jun 8, 2021

Just some unasked-for feedback, but I'd like to see infrastructure/configuration management type code centralised. Preferably in builder.

I absolutely understand the impulse to just write something to get the job done quickly, but that impulse, and the code it generates, spread across time and developers, leads to configuration drift and a sort of diffuse mountain of unmaintained code that is easy to ignore and perpetuates more of the same.

Github configuration can be done through Terraform and Builder uses Terraform. Builder gets less attention because configuration management is being pushed into these scripts, probably because Builder is written in Python and has become unapproachable and a little gnarly over the years. Builder's friendliness can be improved.

Other Github configuration that would be good to capture would be teams and team permissions.

@NuclearRedeye
Copy link
Contributor Author

Just some unasked-for feedback, but I'd like to see infrastructure/configuration management type code centralised. Preferably in builder.

Absolutely. This is just a draft that I threw up to stash the code for safe keeping and I don't have any intention of merging it.

Github configuration can be done through Terraform and Builder uses Terraform

When I come around to looking at this again, I'll take a look.

Other Github configuration that would be good to capture would be teams and team permissions.

I thought similar as I quickly knocked this up and actually took a look at what could be done with the GitHub API. It's quite comprehensive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants