GitHub Enterprise Cloud (data residency) – Gotchas
GitHub Enterprise Cloud with data residency runs an organization's GitHub in the cloud on a dedicated *.ghe.com subdomain, where every host — including OAuth and the REST API — is served from the tenant's subdomain instead of github.com.
2 gotchas across 1 resource
These are connector-specific behaviors and limitations to be aware of when integrating.
Collection Tickets2 gotchas
collectionTicketsAddGitHub always creates issues with status open; the status field is ignored on creation (you cannot create a closed or in-progress ticket). Change it afterward with an update — and note GitHub only supports open/closed. For workflow states like "in progress" or "up next", use labels via the tags field, or GitHub Projects.
collectionTicketsUpdateGitHub issues only support the statuses open and closed. Any other status value (e.g. in_progress) is silently ignored and the issue's state is left unchanged. To represent workflow states like "in progress" or "up next", use labels via the tags field, or GitHub Projects (which are not exposed through this connector).