Source control providers

WhyGraph's remote crawl enriches your scan with pull requests and issues. You choose the backend with [scan].provider in whygraph.toml. Today there's one supported provider - GitHub - with others on the way.

Looking for the LLM providers?

This page is about source-control hosts. For the model adapters behind [analyze], [rationale], and [chat], see LLM providers.

GitHub - supported

Set the provider to github to pull PRs and issues from the GitHub remote:

[scan]
provider = "github"

Or let WhyGraph detect it from your remote URL:

[scan]
provider = "auto"     # detect from the remote (github only, for now)
remote = "origin"     # the git remote whose URL is inspected

The crawl uses the gh CLI, so you need it authenticated. Provide a token one of three ways, checked in this order - the first one found wins and is exported as GH_TOKEN for that scan's gh calls:

1. [scan].token in whygraph.toml - handy when one container scans repos across different orgs.
2. GH_TOKEN or GITHUB_TOKEN in your environment.
3. An existing gh auth login.

Off by default

provider defaults to "off", so a fresh scan stays git-only and needs no token. Opt into the remote crawl by setting github or auto. You can also skip it per-run with whygraph scan --no-remote.

--no-remote also disables PR-origin recovery, which needs the network to fetch a squash-merged PR's original head. The same applies whenever no GitHub client resolves, whatever --pr-origins says.

Upcoming

Other hosts are planned, not yet built. Until they land, point WhyGraph at a GitHub remote or run git-only with provider = "off".

Provider	Status
GitHub	Supported
Azure DevOps	Upcoming
GitLab	Upcoming
Forgejo	Upcoming
Others	Under consideration

See the Roadmap for the broader picture.