GitHub Integration
Authentication Mechanism: Personal Access Token (PAT)
Phase 1: User Request (Token Generation)
Access Developer Settings:
Log in to GitHub and navigate to Settings (via your profile icon).
In the left-hand sidebar, scroll to the bottom and select Developer settings.
Select Personal access tokens → Fine-grained tokens.
Configure Token Identity:
Click Generate new token.
Token name: Use a clear naming convention, such as
[Capacity-AnswerEngine-Token].Expiration: Select an appropriate lifecycle (30, 60, or 90 days is standard for security compliance).
Define Resource Ownership:
Under Resource owner, select the target Organization from the dropdown menu.
Define Repository Scope:
Select Only select repositories.
Choose the specific repositories required for ingestion.
Configure Permissions:
Expand the Repository permissions section.
Select Contents to
Read-onlyMetadata access is automatically set to
Read-onlyand is required for all tokens.
Submit Request:
Click Generate token. You will receive a notification that the token is "Pending" until an Organization admin approves it.
Phase 2: Administrative Review & Approval
Because the token is owned by the Organization, an administrator must authorize its creation to ensure it meets security standards.
Navigate to Organization Settings:
Switch to the Organization view in GitHub.
Click on the Settings tab in the top navigation bar.
Review Pending Requests:
On the left sidebar, locate the Personal access tokens section and click Pending requests.
Audit and Authorize:
Review the requested permissions and repository access for the token.
Click Approve to activate the token. The requesting user will be notified once the token is live and ready for use.
