Configure the repository
Add a root `.gpwiki` file to define the source paths, exclusions, wiki directory, and review policy for the repository.
GPDoc service
Git Knowledge Service turns an authorized GitHub repository into a source-grounded knowledge layer. It keeps Git-tracked files authoritative, returns citations with every result, and keeps wiki updates in the review path your team already uses.
How it works
Add a root `.gpwiki` file to define the source paths, exclusions, wiki directory, and review policy for the repository.
A repository owner or organization administrator installs the GitHub App and chooses which repositories the service can access.
GPDoc indexes eligible text at a specific Git revision. The index is rebuildable and does not replace the repository source.
Keyword and semantic retrieval return paths, revisions, excerpts, and source locations. Wiki maintenance uses a pull request by default.
Why teams use it
Results point back to the repository path and revision instead of presenting an uncited answer as the source of truth.
Generated `.wiki/` pages are separate from source files. Default updates are visible in a dedicated branch and pull request.
The service checks authorization and applicable entitlement before it reads, indexes, or searches a private repository.
Service boundary
The managed service is entitlement-aware. It protects private repositories and checks access before it performs indexing or retrieval.
Add `.gpwiki`, install the GitHub App for the repositories you choose, and use GPDoc to keep the resulting knowledge layer connected to source.