Skip to content

Add NEXT_GITHUB_READ_API_TOKEN to PERMISSIONS.md#127

Open
MattIPv4 wants to merge 1 commit intomainfrom
MattIPv4/next-github-read-token
Open

Add NEXT_GITHUB_READ_API_TOKEN to PERMISSIONS.md#127
MattIPv4 wants to merge 1 commit intomainfrom
MattIPv4/next-github-read-token

Conversation

@MattIPv4
Copy link
Copy Markdown
Member

Copilot AI review requested due to automatic review settings April 12, 2026 22:44
@MattIPv4 MattIPv4 requested a review from a team as a code owner April 12, 2026 22:44
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository permissions documentation to include the NEXT_GITHUB_READ_API_TOKEN secret used by the production Vercel deployment for Node.js website GitHub Sponsors fetching, aligning with the referenced discussion in nodejs/nodejs.org#8531.

Changes:

  • Adds NEXT_GITHUB_READ_API_TOKEN to the “Access Tokens & Automations” table.
  • Documents its location (Vercel production) and required permission scope (read:org).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@MattIPv4 MattIPv4 force-pushed the MattIPv4/next-github-read-token branch from b3ba9ea to 3bd58df Compare April 12, 2026 22:46
@MattIPv4 MattIPv4 force-pushed the MattIPv4/next-github-read-token branch from 3bd58df to 3418b5f Compare April 12, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants