Skip to content
Discussion options

You must be logged in to vote

Hey, I can see why this is frustrating. The connection between GitHub and Google Gemini can be a bit finicky, especially with private repos.
So here's the thing, even though you've connected both sides, there's usually a step that gets missed. After you've authorized the Google integration on GitHub and given it access to your private repo, you need to make sure that specific repository is actually selected in the integration settings. Sometimes the connection shows as "active" but the repo permissions aren't fully synced yet.
Try going back to your GitHub settings, then navigate to Applications under Integrations, and find the Google/Gemini integration there. Click into it and double, ch…

Replies: 3 comments 12 replies

Comment options

You must be logged in to vote
2 replies
@DickHannay
Comment options

@FOOSAYS
Comment options

Answer selected by DickHannay
Comment options

You must be logged in to vote
3 replies
@DickHannay
Comment options

@SithLord2K
Comment options

@arjunghosh
Comment options

Comment options

You must be logged in to vote
7 replies
@fransai
Comment options

@ethan-ghoreishi
Comment options

@nicholasxng
Comment options

@pasza01
Comment options

@denikatsman
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage Question Ask and answer questions about GitHub features and usage