Clarify authentication headers for GitHub/GitLab

[Proce2]

Changes

• Changed "GitHub access" → "repository access"
• Changed <GITHUB_TOKEN> → <ACCESS_TOKEN>
• Fixed "Gitlab" → "GitLab" capitalization

Why

Makes it clearer that the same X-GitHub-Token header works for both GitHub and GitLab tokens.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[greptile-apps-staging]

Greptile Summary

This PR makes targeted documentation improvements to clarify authentication requirements in the API reference. The changes address potential confusion around token usage by updating terminology from "GitHub access" to "repository access" and replacing the specific <GITHUB_TOKEN> placeholder with the more generic <ACCESS_TOKEN>. Additionally, it corrects the capitalization of "GitLab" for brand consistency.

These changes integrate well with the existing documentation structure by making the authentication section more accurate and inclusive. The modifications reflect that the X-GitHub-Token header accepts both GitHub and GitLab access tokens, which is an important clarification for users working with GitLab repositories through the API.

Important Files Changed

Changed Files

Filename	Score	Overview
api-reference/introduction.mdx	5/5	Updated authentication documentation to clarify that repository access tokens work for both GitHub and GitLab

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it only contains documentation clarifications
• Score reflects simple, non-functional changes that improve accuracy without affecting any code behavior
• No files require special attention as this is purely a documentation update

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}