Why connect GitHub?
When you're planning what to build, knowing your codebase matters. With GitHub connected, you can ask the AI chat assistant questions about your code, and ProductBet can generate more specific implementation plans for your bets.
What GitHub provides
- Codebase questions in Chat - ask about architecture, specific files, how features are implemented
- Smarter implementation plans - when generating an execution plan for a bet, ProductBet reads your codebase to suggest specific files and components to modify
How to connect
Go to Settings > Integrations > GitHub and enter your personal access token (with repo read access), along with the owner and repository name. Click Save.
Creating a GitHub personal access token
- Go to github.com > Settings > Developer Settings > Personal Access Tokens
- Create a new token with
reporead access - Copy the token and paste it into ProductBet
Using GitHub with Chat
Once connected, go to Chat and ask codebase questions:
- "How is authentication implemented?"
- "What does the API endpoint for creating users look like?"
- "Where is the billing logic handled?"
- "What database schema does the user model use?"
- "How is the notification system structured?"
The assistant searches your repository and returns relevant code and explanations.
Using GitHub with bet execution plans
When you generate an AI implementation plan for a bet (from the Execution tab), ProductBet will:
- Explore your repository structure
- Identify relevant files and components
- Suggest specific files to modify
- Reference real file paths in the task descriptions
This makes implementation plans much more actionable than generic suggestions. An AI provider must be configured for this feature.
Troubleshooting
- Chat says GitHub is not connected? Check that you've entered your access token, owner, and repository name on the GitHub integration page.
- Can't find code? Make sure the access token has read access to the repository and that the owner/repo values are correct.
- Token expired? GitHub personal access tokens can expire. If the integration stops working, generate a new token and update it on the GitHub integration page.