​

GitHub Integration

BuildBetter’s GitHub integration allows you to create issues, link repositories, and reference code directly from your meeting recordings, streamlining your development workflow from discussion to implementation.

​

Features

• Issue Creation: Create GitHub issues directly from meeting recordings
• Repository Linking: Connect recordings and documents to specific repositories
• Pull Request References: Link discussions to relevant pull requests
• Code Snippet Extraction: Extract and reference code discussions
• Automated Workflows: Trigger GitHub actions based on meeting content

​

Setup Instructions

​

Prerequisites

• An active BuildBetter account
• GitHub account with appropriate repository access
• Admin permissions in BuildBetter

​

Connecting GitHub

1. Navigate to Settings → Integrations in your BuildBetter dashboard
2. Select GitHub from the project integrations
3. Click Connect and authorize via GitHub OAuth
4. Select which repositories to enable for integration
5. Configure default settings and permissions

​

Repository Configuration

After connecting:

1. Go to Settings → Integrations → GitHub → Repository Settings
2. Configure:
   • Default repositories
   • Issue templates mapping
   • Label defaults
   • Automatic reference formatting
3. Save your repository configuration

​

Usage

​

Creating Issues from Meetings

Create GitHub issues while in a meeting:

1. Open any call recording in BuildBetter
2. Select a relevant segment in the transcript
3. Click the Create Issue button
4. Select the target GitHub repository
5. Fill in issue details, leveraging transcript content
6. Submit to create the issue in GitHub

​

Linking to Repositories

Connect meetings to specific repositories:

1. From any recording or document, click Link Repository
2. Select the GitHub repository from your connected list
3. Optionally, add a reference note
4. Save to establish the connection

​

Code Discussion References

Link code discussions to GitHub:

1. During transcript review, identify code-related discussions
2. Use the Code Reference button in the transcript
3. Select the relevant GitHub repository, branch, and file
4. Add line number references if applicable
5. Save to create a two-way reference

​

Advanced Features

​

Signal Analysis

BuildBetter’s Signals feature can automatically detect:

1. Feature requests for GitHub issue creation
2. Bug reports for immediate tracking
3. Technical discussions for documentation
4. Decision points for project planning

Configure how these signals interact with GitHub:

1. Go to Settings → Integrations → GitHub → Signals
2. Map signal types to GitHub actions
3. Set thresholds and trigger conditions
4. Enable automation for selected signals

​

Automated Issue Creation

Set up rules for automatic GitHub issues:

1. Navigate to Settings → Automation Rules
2. Create rules based on:
   • Meeting tags or topics
   • Specific phrases in transcripts
   • Participant roles or departments
3. Configure how issues should be formatted
4. Test and enable your automated workflow

​

Troubleshooting

​

Connection Issues

• Verify your GitHub authentication is current
• Check repository access permissions
• Ensure you haven’t hit API rate limits

​

Issue Creation Problems

• Verify required fields in issue templates
• Check for any GitHub organization restrictions
• Ensure proper repository permissions

​

Repository Access

• Review GitHub organization settings
• Check personal access token scopes (if applicable)
• Verify BuildBetter has been authorized for the specific repositories

​

Use Cases

​

Engineering Teams

• Create implementation tickets directly from planning meetings
• Reference architecture discussions in documentation
• Link technical decisions to relevant code changes

​

Open Source Projects

• Extract feature requests from community meetings
• Document decisions with links to relevant discussions
• Create transparent issue trails from conversation to code

​

DevOps Workflows

• Link incident response calls to GitHub issues
• Create post-mortem documentation with meeting references
• Track resolution from discussion to implementation

​

Security Considerations

• BuildBetter uses GitHub’s OAuth for secure authentication
• Repository access is limited to those explicitly granted
• Private repository content remains secure
• No code is stored in BuildBetter, only references to GitHub