-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Configure Github with Terraform #398
Comments
I've already been looking at this, short term it seems good but I'm a bit concerned that it will end up being a burden to maintain long term. At the moment I'm thinking about dumping the org api daily and pushing it to a repo, which would give us a transparent log. |
We could start with partial coverage. One thing that would be good is to have this 1:1 mapping between teams and repo names. |
https://github.com/ipdxco/github-as-code (from https://github.com/NixOS/org) This looks like it could be good but:
May need to use gitlab for state or self host (IIRC all of the other free TACOS have some sort of resource/user limit), would also want to keep state locking. |
We have the Settings app for repository owners to self-configure their repos.
What's missing is to describe all of the teams and members as code to increase transparency even further.
That also helps create a membership list, potentially allow members to send PRs to add new repos, ...
The text was updated successfully, but these errors were encountered: