Nick Floyd

@scottluskcis @stevehipwell I'd be good with either way, though now changing it might technically be a breaking change - candidly I prefer the singleton approach, @stevehipwell reminded me of that...

This feels like another `destroy_on_drift` scenario much like this recent [changeset](https://github.com/integrations/terraform-provider-github/pull/1351). My guess from the discussion is that we need to add the property to `resourceGithubActionsSecret` for those who want...

Hey @MatisseHack, This is one of the future design changes we hope to make as we begin leaning into generative SDKs - we'd like to abstract things such as models,...

@stevehipwell I am actively working to get some much needed change sets merged in and eventually released. Given the age, nature, and variation of these changes I have some CI...

> @nickfloyd have you looked at #2476? I worked through all of the tests to fix them, changes since the PR was last rebased likely need integrating. I haven't just...

Hey @zaMedvedem thanks for tracking this down and sorry for the trouble. Let us know if you'd be interested in fixing the issue and submitting a PR. For now I...

Hey @Robert-Wright-NTT thanks for reaching out. So I think what you're looking for is the [org pending invite endpoints](https://docs.github.com/en/rest/orgs/members?apiVersion=2022-11-28#list-pending-organization-invitations) from the GitHub REST API. This functionality is present in both...

Merging this in as a preventative measure since this is a manually generated SDK. These changes, while breaking should have a nominal impact on usage.

Restating what I understand the core issue to be - basically when users archive a GitHub repository, the provider attempts to delete managed resources (like issue labels -as in the...

This is what I was thinking: https://github.com/integrations/terraform-provider-github/pull/2837 I'm not sure it will matter but I need to think through the behavior of when users "unarchive" repos. I think it should...