feat: add personal access token authentication #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove /api/auth/validate-token server endpoint - Validate PAT directly against GitHub API from client (CORS supported) - Enforce repo scope requirement with clear error message - Improve PAT input UI with cleaner layout and better UX - Add escape key to cancel, autofocus input field
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
tested this locally and works great |
Contributor
|
do you think we can get this merged @kylecarbs? |
Contributor
|
Just checking in, are there any plans ot merge this? |
Member
|
Oops, sorry @pepegar! Looking now. |
kylecarbs
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Personal Access Token (PAT) authentication, allowing users to sign in without going through the OAuth device flow.
Based on #12 by @pepegar, with the following improvements:
reposcope before accepting itChanges
loginWithPATfunction to auth context that validates tokens directly with GitHub APIghp_(classic) andgithub_pat_(fine-grained) token formatsHow it works
https://api.github.com/user(CORS is supported)x-oauth-scopesheader to ensurereposcope is presentCloses #12