feat: Add repository-scoped token support to GithubAppClient #258
+142
−0
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.
Summary
Adds support for creating repository-scoped installation access tokens via the GitHub Apps API. This allows tokens to be
restricted to specific repositories instead of granting access to all repositories in an installation.
This is an implementation of https://docs.github.com/en/rest/apps/apps#create-an-installation-access-token-for-an-app
API Usage
Testing
Unit Tests
All existing tests pass, plus 3 new test cases:
Manual Testing
Verified end-to-end with GitHub Enterprise Server:
Test 1: Unscoped Token (`Old Behavior)
Created token using existing
getAccessToken(installationId)methodVerification via GitHub API:
Test 2: Repository-Scoped Token (New Functionality)
Created token using new getAccessToken(installationId, AccessTokenRequest) method:
Verification via GitHub API:
✅ Token granted access to only 1 repository (the scoped repository)