Github Integration Issues

[buoyant trail]

Hi @north zephyr. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

That's a known friction point when setting up the GitHub integration. Based on the available documentation, here are a few things to check:

Verify Repository Access is Properly Configured

The Trigger.dev GitHub app needs explicit repository access granted on the GitHub side. Even if the app appears "connected," the specific repository may not be authorized. To check and update this:

1. Go to your GitHub account settings
2. Navigate to Settings → Applications → Installed GitHub Apps
3. Click Configure next to Trigger.dev App
4. Under Repository access, make sure your repository is listed and authorized

Changes to repository access will be reflected immediately in your Trigger.dev project settings. [Managing repository access]

Connect the Repository from the Trigger.dev Dashboard

After confirming access on GitHub, you'll also need to explicitly connect the repository within Trigger.dev:

1. Go to your project's settings page in the Trigger.dev dashboard
2. Click Install GitHub app (if not already done)
3. Use the Connect GitHub repository modal to select your repository [GitHub integration]

The key thing to note is that granting access on GitHub and connecting the repo inside Trigger.dev are two separate steps — both need to be completed for the dashboard to recognize the connection.

If you've done both of these and the dashboard still doesn't reflect the connection, the knowledge sources don't contain further troubleshooting steps for this specific scenario. I'd recommend reaching out via the Trigger.dev GitHub issues for additional support.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: