1. Docs
2. Reference
3. REST API Docs
4. Schema
5. VCSGitHubAccessResponse

VCSGitHubAccessResponse describes a user’s GitHub access status for VCS integrations.

Properties

• hasUserToken boolean required
  Whether the user has a GitHub user token.
• hasIntegration boolean required
  Whether the user has a GitHub app installed.
• availableOrgs array[string] required
  The list of GitHub organizations available to the user.
• integrations array[GitHubIntegrationPermissions] optional
  Per-integration permissions for the current user
• ↳ id string required
  Pulumi installation ID
• ↳ canCreateRepo boolean required
  Whether the user can create repos under this installation
• ↳ canCreateRepoReason enum optional
  Why the user cannot create repos under this installation, when canCreateRepo is false. Null when they can, or when the reason could not be determined. Creating a repository writes as the user’s own GitHub identity, so the answer is often about which GitHub account is connected rather than about permissions, and each cause has a different remedy. Clients should treat an unrecognized value as a generic unavailable case.
  Values: internalError, appNotInstalled, badCredentials, accountNotOrgMember, individualAccessRequired, selectedReposOnly, repoCreationDenied