> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub Integration

> Use GitHub repositories as workspace-scoped API context for Woes agents and operators.

# GitHub Integration

<img src="https://mintcdn.com/woes/SjmqB9Aiw359c6aC/images/integrations/github-logo.svg?fit=max&auto=format&n=SjmqB9Aiw359c6aC&q=85&s=5b8c00c604ddc4332ffc0223612d7a63" alt="GitHub logo" width="56" height="56" data-path="images/integrations/github-logo.svg" />

GitHub brings repository knowledge into Woes so operators and agents can answer
from the examples, docs, SDK notes, and migration guidance your developers
already maintain.

## At A Glance

| Use GitHub for                                                                | Where it appears                                                                      |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Repository docs, examples, SDK guides, changelogs, and troubleshooting notes. | Context Library, agent source selection, and retrieved evidence in support workflows. |

## What it does

GitHub helps Woes answer support questions with source-adjacent evidence from your repositories:

* README files and docs folders
* SDK examples and sample applications
* Changelog notes and migration guides
* Troubleshooting notes that live beside code
* OpenAPI, Postman, GraphQL, AsyncAPI, gRPC, or SOAP artifacts stored in the repo

Imported repository content becomes a Woes context source. Agents can retrieve it alongside API docs, websites, pasted context, and other workspace sources.

## Where it appears in Woes

* **Workspace Settings -> Integrations** shows GitHub connection state.
* **Context Library** is where operators connect GitHub, import repositories, rescan sources, inspect indexed files, and disconnect the OAuth account.
* **Agent context selection** can attach GitHub-backed sources to specific agents.

## Data And Access

Woes reads only the repositories and files selected by the workspace. The
workspace UI shows safe account and repository details, not private connection
credentials. Disconnecting GitHub stops new repository imports; already-indexed
Woes sources remain until the workspace deletes them.

<Tip>
  Import repositories that explain product behavior, not every repository your
  company owns. Smaller, focused sources are easier for agents and operators to
  trust.
</Tip>

## Good first use cases

* Add repository examples that explain how customers should call your API.
* Import SDK docs that are more practical than the OpenAPI contract alone.
* Give the support agent migration notes that customers often ask about.
* Link a GitHub source to a formal API source when repo examples explain the same product surface.

## Related docs

* [GitHub Context](/context/github)
* [Sources](/context/sources)
* [Knowledge Base Overview](/knowledge-base/overview)