-
Notifications
You must be signed in to change notification settings - Fork 776
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
Team reviewers exclusions #1965
base: main
Are you sure you want to change the base?
Conversation
@kfcampbell I started working on adding functionality for this issue and quickly realized that it's currently limited by the API, which is currently in preview. While it's possible to to SET the exclusion list, it's not possible to read it. This leads to terraform never being able to make proper plans, since the exclusion list always will be empty from the providers perspective: My question now is whether you're able to ask around to see what the maturity plan is for the GitHub team GraphQL API is? I could spend some time trying to work around the issue, but the "proper" solution is just for the read of the exclusion list to be added to the API. If that's upcoming in the pipeline, I don't think whatever hack I come up with is the way to solve it. It seems like it's been in preview since at least |
I totally agree with you. I don't think it's worth hacking around until it's available in the API. Unfortunately I don't have any insight as to the plan there. Logging a public request here is probably the best bet. |
I've added a discussion about it here: https://github.com/orgs/community/discussions/72860 |
Hello, just saw some activity on the discussion page, do you know if this is mergeable @felixlut ? |
@Rowern no, sadly it's not in a mergeable state. A month or so ago I got back to this and checked again if the API needed for this feature was available now, as the reply to my discussion suggested. It was not. It isn't now. The API is no longer in preview though, which is something. I've tried reaching out again here, but haven't seen an update since. |
Resolves #1972
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?