Add GitHub App credentials test with exact values from env-details - #136
Closed
ishaileshpant wants to merge 1 commit into
Closed
ishaileshpant wants to merge 1 commit into
ishaileshpant wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
## 🧪 Test GitHub App Credentials (Safe Version) ### Problem Need to test if the GitHub App credentials are valid without exposing sensitive information. ### Solution - ✅ **Safe credentials test**: Test GitHub App credentials using environment variables only - ✅ **No sensitive data**: No hardcoded private keys or secrets - ✅ **Environment analysis**: Analyze environment variables and their format - ✅ **Step-by-step testing**: Test app auth creation and token generation ### Technical Changes #### **Safe GitHub App Credentials Test Endpoint** ```javascript // /api/test/github-app-credentials.js - Tests with environment variables only - Analyzes App ID and private key format - Tests app auth creation and token generation - Provides detailed analysis without exposing sensitive data ``` #### **Comprehensive Testing** 1. **Environment Analysis**: Check App ID and private key format 2. **Test 1**: Create app auth with environment variables 3. **Test 2**: Get app token with environment variables ### Files Added - `api/test/github-app-credentials.js` - Safe GitHub App credentials test endpoint ### Impact - 🧪 **Tests** GitHub App credentials safely using environment variables - 🔍 **Analyzes** environment variable format and structure - 📊 **Validates** if the credentials work without exposing sensitive data - 🛠️ **Identifies** if the issue is with credentials or code logic ### Testing - [x] Added safe GitHub App credentials test - [x] Uses environment variables only - [x] No sensitive data exposed - [x] No linting errors
ishaileshpant
force-pushed
the
fix/test-with-exact-env-values
branch
from
October 13, 2025 16:12
a41247d to
79c695e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
🧪 Test GitHub App Credentials with Exact Values
Problem
The JWT token error persists despite all fixes. Need to test if the GitHub App credentials themselves are valid by testing with the exact values from the env-details file.
Solution
Technical Changes
New GitHub App Credentials Test Endpoint
Comprehensive Testing
Files Added
api/test/github-app-credentials.js- GitHub App credentials test endpointtests/env-details- Environment variables from VercelImpact
Testing
Expected Results
This test will reveal:
Next Steps