Skip to main content

​
GitHub Context

GitHub repositories can be used as context sources. This is useful when your API support knowledge lives near code, SDK examples, docs folders, sample apps, or README files.

​
Before You Connect

GitHub import needs to be enabled for your Woes workspace. If the GitHub card or import window says Setup needed, contact your workspace admin or Woes support before trying to authorize repositories. You also need access to the GitHub account or organization that owns the repository. Woes can only list repositories that GitHub grants to the authorized connection.

​
Setup Flow

1

Connect GitHub

Open the GitHub integration from Context and authorize access.
2

Choose a repository

Pick the owner and repository that should be scanned.
3

Filter if needed

Search the repository list when you have access to many repos. Private repositories display with a lock icon.
4

Create the source

Woes creates a github source with repository metadata.
5

Scan files

Woes scans the repository default branch for supported documentation-like files and builds repository file documents.
6

Attach to an agent

Add the repository source to the agent that should answer from that material.

​
Good Repository Content

  • README.md files.
  • Docs folders.
  • SDK examples.
  • API usage examples.
  • Error-handling guides.
  • Authentication examples.
  • Webhook examples.

​
What Woes Scans

Repository ingestion prioritizes documentation-oriented files from the default branch, such as Markdown, MDX, docs folders, README files, OpenAPI/spec files, examples, and SDK usage notes. It is designed to build support context, not to index arbitrary private application code as a customer-facing answer source. The current GitHub import flow does not expose branch or folder selection in the app. If different docs branches or folders matter, prepare a repository layout where the default branch contains the production support material you want agents to use. After import, open the created source in Context to review the scanned files, source status, and any partial-ingestion warnings before attaching it to an agent.

​
Security Notes

Woes keeps the GitHub connection server-side and only shows safe account and repository metadata in the app. Attached repository content can become support evidence for agents, so treat selected repositories and branches as customer-support source material.
Do not attach repositories, branches, docs, code comments, or examples that contain secrets, private customer data, unreleased behavior, or anything that should not influence customer-facing support answers. Woes redaction and grounding safeguards are not a substitute for source hygiene.
Last modified on July 4, 2026