Skip to content

Draft: add server-backed GitHub data access#100

Draft
SakshiKekre wants to merge 2 commits intomainfrom
fix/server-side-github-token
Draft

Draft: add server-backed GitHub data access#100
SakshiKekre wants to merge 2 commits intomainfrom
fix/server-side-github-token

Conversation

@SakshiKekre
Copy link
Copy Markdown

Summary

  • adds a narrow Next.js API route for the dashboard's GitHub data reads
  • updates the dashboard to call the internal route instead of GitHub directly
  • removes static export mode so the route can run on Vercel

Notes

This is a draft because it changes the dashboard from static export output to a server-backed Next.js deployment. Reviewers should confirm that deployment model is acceptable before this is merged.

Configuration

Set one server-side Vercel environment variable:

  • GITHUB_TOKEN or GITHUB_CONTENTS_READ_TOKEN

Optional:

  • GITHUB_ALLOWED_OWNERS, defaults to PolicyEngine

Verification

  • npm run build

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
microcalibrate Ready Ready Preview, Comment Apr 21, 2026 3:18am

Request Review

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.

1 participant