Select repositories
Choose which installed repositories become available to approved research workflows.
Index selected GitHub repositories so Docpipe can research implementation details and create cited technical write-ups.
Northwind uses Keyward for identity, with edge session refresh and tenant-scoped access controls.
services/gateway/auth-guard.tsdb/policies/..._access_rules.sqlWhy it matters
The GitHub integration grounds documentation workflows in repository context. It helps Docpipe search, read, and cite code while leaving the repository itself unchanged.
Each capability is useful on its own. Together, they make documentation easier to create, trust, and reuse.
Choose which installed repositories become available to approved research workflows.
Prepare code files and metadata for semantic and exact search.
Trace system behavior across files, symbols, and related internal documentation.
Write the result into a Docpipe space with source references.
How it works
No content graveyard. No magic black box. Each step has an understandable output and owner.
Authorize access to the repositories you choose.
Docpipe prepares supported repository content for search.
Run an exhaustive inventory or an open-ended technical investigation.
Open the resulting write-up and verify its citations.
Common questions
No. The current GitHub integration is used to index selected content for search and documentation workflows.
Refresh behavior depends on the current indexing schedule and webhook configuration. Confirm the production cadence during setup.
The indexer includes safeguards and file filters, but organizations should still follow standard secret-management practices and review repository selection carefully.
Tell us about your team and we’ll confirm the right path to a Docpipe workspace.
Connect GitHub ↗