GitHub Integration
Connect your GitHub repositories to SprintFlint to automatically link pull requests to issues, create branches, and track code changes.
Connecting GitHub
To connect your organisation to GitHub:
- Click your avatar in the sidebar
- Go to "Organisation Settings"
- Click "Connect GitHub"
- Authorise SprintFlint to access your repositories
Permissions - SprintFlint requests read access to your repositories. We use this to detect pull requests and link them to issues. We never modify your code.
Linking a Repository to a Project
After connecting GitHub at the organisation level, link specific repositories to projects:
- Navigate to your project settings
- Select a repository from the dropdown
- Save the project
Automatic PR Detection
SprintFlint automatically detects pull requests and links them to issues by scanning for your issue number (e.g., PROJ-123) in:
- Branch name - e.g.,
feature/PROJ-123-user-auth,proj-123-auth,proj123 - PR title - e.g., "PROJ-123: Add user authentication"
- PR description - e.g., "This PR implements PROJ-123"
Common keywords like fixes, closes, or resolves are supported but optional - the issue number alone is enough.
Creating Branches
SprintFlint can create branches for issues directly from the UI:
- Open an issue
- In the sidebar, click "Create Branch"
- SprintFlint creates the branch and opens GitHub Desktop
Branch Naming
When creating a branch via SprintFlint, or using the Autoplay feature, the branch is automatically named using your project prefix followed by the issue number and AI generated title. For developers, they just need to either reference the issue number or include it in the branch name. E.g.:
{prefix}{issue-number}-{kebab-case-title}
For example:
- With prefix
sf-:sf-123-add-user-authentication - With prefix
PROJ-:proj-123-add-user-authentication
Pull Request Status
Once a PR is linked to an issue, you'll see:
- PR title - The pull request title
- Status - Open, Merged, or Closed
- Link - Direct link to the PR on GitHub
Webhooks
SprintFlint uses GitHub webhooks to receive real-time updates about pull requests. When you connect a repository, we automatically create a webhook.
Webhook Permissions - You need admin access to the repository to create webhooks. If you don't have admin access, ask a repository administrator to connect the integration.
Disconnecting GitHub
To disconnect GitHub:
- Go to "Organisation Settings"
- Click "Disconnect GitHub"
- Confirm the disconnection
Disconnecting will:
- Remove the stored access token
- Delete webhooks from connected repositories
- Preserve existing PR links (as historical data)
Troubleshooting
PRs Not Being Detected
If pull requests aren't being linked automatically:
- Ensure the repository is linked to the correct project
- Check that your issue number format matches the project prefix
- Verify the webhook is active in GitHub (repository Settings → Webhooks)
Permission Errors
If you see permission errors:
- Re-authorise the GitHub connection
- Ensure you have access to the repository
- Check that the repository hasn't been renamed or deleted
Next Steps
- Autoplay - Let AI create PRs automatically
- API Reference - Integrate with your own tools