GitHub REST API connector boundary

Evidence-backed facts

1. Some GitHub REST endpoints expose public information without authentication, while authenticated requests can access additional endpoints and rate limits. informative
2. Write operations require the endpoint's declared token permissions and remain separate from repository, organization, branch, or environment policy. informative
3. GitHub supports personal access tokens, GitHub App tokens, and workflow GITHUB_TOKEN credentials; fine-grained tokens are recommended where supported. informative
4. A token is an identity-bearing secret, and endpoint documentation plus accepted permissions must be checked before every read or mutation is exposed. informative

Primary sources