Keegan Campbell

That's awesome news! Pull requests are very welcome for this feature.

Hmm...I don't think this is true as a blanket statement. Our [Enterprise Cloud docs](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise) mention that IdP _can_ be enforced for an organization, but don't have to be, and our...

> Do you have a list of the currently broken acceptance tests We don't have a comprehensive list of broken acceptance tests unfortunately. As the suite hasn't been run front-to-back...

I'm seeing failing integration tests as a result of these changes: ``` --- FAIL: TestAccGithubRepositoryVisibility (63.14s) --- PASS: TestAccGithubRepositoryVisibility/creates_repos_with_private_visibility (7.82s) --- SKIP: TestAccGithubRepositoryVisibility/creates_repos_with_private_visibility/with_an_anonymous_account (0.00s) --- SKIP: TestAccGithubRepositoryVisibility/creates_repos_with_private_visibility/with_an_individual_account (0.00s) --- PASS:...

Unfortunately, this feature is not released on the API yet. Once support is added in the API, we can implement it in the provider.

Ideally there would be more than just a GET. We could make a data source with the existing endpoint, but not a full resource.

Ahh my mistake, thanks for correcting me!

GitHub's SDK team unfortunately does not have the bandwidth to take this on ourselves, though we're very receptive of PRs!

It's worth noting that we (GitHub's SDK team) are working on a [Go SDK](https://github.com/octokit/go-sdk) generated from GitHub's OpenAPI specification. It includes all routes published in the GitHub API, so coverage...

Hmm...I'm somewhat partial to `gh_cli_user` as it makes it clear the authentication is coming from the `gh` CLI in the normal scenario. Thoughts?