Skip to main content

Overview

The GitHub connector lets you link your GitHub account to Workshop using a Personal Access Token. Once connected, you can access repositories, analyze code, clone repos, and perform API operations through natural conversation.

What You’ll Need

CredentialDescriptionFormat
Personal Access TokenFine-grained or classic GitHub tokenghp_... (classic) or github_pat_... (fine-grained)

Creating a Personal Access Token

1

Open GitHub settings

Sign in to github.com, click your profile photo, and select Settings.
2

Navigate to developer settings

Scroll down the sidebar and click Developer settings > Personal access tokens > Fine-grained tokens.
3

Generate a token

Click Generate new token. Enter a Token name (e.g., “Workshop Access”), set an Expiration date, and choose the Resource owner (your account or an organization).
4

Set repository access

Under Repository access, select which repositories the token can access.
5

Set permissions

Under Permissions, grant the access you need:
  • Contents: Read (to view files)
  • Metadata: Read (required for all tokens)
  • Issues: Read and write (if you want Workshop to create/manage issues)
  • Pull requests: Read and write (if you want Workshop to create PRs)
6

Copy the token

Click Generate token and copy it immediately. GitHub only shows the token once.
Organization tokens may require approval. If you select an organization as the resource owner, the organization may need to approve the token before it becomes active. Check with your organization administrator if the token isn’t working.

Connecting to Workshop

1

Open the Hub

Open the Workshop Hub from the sidebar.
2

Go to Connectors

Click the Connectors tab.
3

Select GitHub

Click the GitHub card.
4

Enter details

Enter a Connection Name (e.g., “My GitHub Account”) and paste your Personal Access Token.
5

Save

Click Add Connection.

Using Your Connection

Once connected, you can ask Workshop to work with your GitHub data:
Using my GitHub connection, list all my repositories
Show me the README from my project-name repository
What are the open issues in my app repository?
Using my GitHub connection, clone my website repo and help me understand its structure

Security Best Practices

  • Use fine-grained tokens with the minimum permissions needed
  • Set an expiration date on all tokens
  • Create separate tokens for different integrations
  • If you suspect a token is compromised, revoke it immediately in GitHub Settings > Developer settings > Personal access tokens
GitHub automatically scans for leaked tokens and may revoke them. Never commit tokens to version control or share them publicly.

Troubleshooting

IssueSolution
”Bad credentials”Verify the token was copied correctly and hasn’t expired or been revoked.
”Not Found” for reposEnsure the token has access to the target repository.
Rate limitingGitHub limits API requests to 5,000/hour for authenticated users. Wait for the limit to reset.

Learn More