Your team's GitHub repos hold more than code - README files, wikis, setup guides, architecture docs, contribution guidelines, all written for whoever needs to onboard or debug next. Questions your agent gets asked could often be answered straight from that documentation. Right now, it's locked inside a repo only engineers think to check.

Connecting GitHub gives your agent direct access to that content. No copying files into another tool, no keeping a second version up to date. Your agent reads the documentation where it already lives and uses it to answer questions, staying in sync as it's updated.

In this article, you'll learn:

• What happens when you connect GitHub
• How to connect your GitHub account
• How to manage the connection after it's set up

What Gets Connected

When you connect GitHub, Outlearn syncs the repositories you authorize and uses their documentation as a source of answers. Your files stay exactly where they are - Outlearn reads them, it never modifies or moves them.

Supported content includes README files, wiki pages, and markdown documentation. Source code files are not used as answer content.

How to Connect GitHub

1. Go to the Sources tab.
2. Click + Add Knowledge.
3. In the Add Knowledge Sources modal, click Cloud Storage in the left panel.
4. Select GitHub.
5. Log in to your GitHub account when prompted and authorize Outlearn to access your repositories.
6. Follow the on-screen steps to select which repositories to sync and set accessibility.

After Connecting

Once connected, GitHub will appear in your Sources list. Outlearn will keep it in sync automatically as your repositories change.

From the Sources list you can:

• Change accessibility using the dropdown next to the source.
• Toggle it on or off using the In Use toggle.
• Resync manually using the three-dot menu to force an immediate update.
• Delete the connection using the three-dot menu if you no longer need it.

Best Practices

• Only connect repositories that are relevant to the questions your agent will be answering - connecting every repository in your organization adds noise and can dilute answer quality.
• Use Internal accessibility for private repositories or documentation containing sensitive technical details that shouldn't be shared with public users.
• If you restructure or rename files in a connected repository, trigger a manual resync to make sure the changes are reflected in your agent.Make your GitHub repositories instantly searchable by your agent.