github-as-code
github-as-code copied to clipboard
ipdxco
GitHub Configuration as Code
Right now, both of these might miss some connections due to differences in casing when comparing user/team names
# Ideal I think there should be some tooling that answers for person X: 1. what repos does X have permissions for 2. what permissions does X have on those...
# Problems 1. github-mgmt YAML files can be unwieldy in part because of archived repos (see https://github.com/ipdxco/github-as-code/issues/115). One of the reasons is that the archived repos still have access permissions...
# The problem These .yaml files can be unwieldy and the problem is exasperated by intermixing of archived repos with unarchived repos. # Ideas I think it would be help...
I wish github-mgmt didn’t sort all key alphabetically when there is a more meaningful default. For example, with "collaborators” and “teams”, I want the keys to be in descending order:...
Whenever I have to engage more seriously with github-magement, I end up having to find and open the links below so I can make informed decision. I wish these links...
https://github.com/ipfs/github-mgmt/pull/182#issuecomment-1844802842
When you update the config (by adding a file there which exists in the target repo) and sync, the file is currently not imported to terraform state.
Implement issue labels support efficiently. With https://github.com/integrations/terraform-provider-github/compare/main...galargh:terraform-provider-github:feat/github_issue_labels in place, we can manage all labels for a repository using a single tf resource instead of a resource per label. This greaaaaaaatly...