GitHub Integration
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
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.
Import repositories that explain product behavior, not every repository your
company owns. Smaller, focused sources are easier for agents and operators to
trust.
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.
