Skip to main content
Repositories controls which codebases Graphify indexes. Builds shows the indexing runs that produce their graphs and wiki content.

Connect a repository

Open Repositories in Graphify. Click Add GitHub repositories, or click Connect on the GitLab card in Connectors, then complete the provider’s repository-access flow. Google Drive folders are added from Connectors. Follow Connect Google Drive. If you installed the Graphify GitHub App from github.com, owners and admins see a Claim button on Repositories to connect that install to the workspace. See Claim an install from github.com. Return to the repository list to check indexing status. Provider and status filters help narrow a large workspace.

Repository controls

Open a repository’s … options menu. Controls depend on the provider and your role. Do not use the indexing toggle as a substitute for review configuration.

No longer on GitHub

When GitHub reports a repository as deleted, transferred to an account without Graphify, or no longer accessible to the Graphify GitHub App, the row shows No longer on GitHub. A countdown appears when Graphify will remove it on its own (for example, Removed from Graphify in 5 days). Owners and admins can Remove it from that row to delete its graph and history now. Hover the label for the reason Graphify recorded (access_removed, deleted, or transferred).

Transfers that stay connected

If you transfer a repository to a new owner and Graphify remains installed on that account, the repository keeps its builds, reviews, verifications, and memories. The row stays indexed; it does not show No longer on GitHub.

When a repository is indexed

A push to the repository’s default branch starts an index of that commit. On GitHub and GitLab, the default branch is the branch the provider marks as default, often main. A push to any other branch does not update the graph. Branches named dev or uat are not indexed unless one of them is the default branch. Nothing from a pull request’s branch is saved as an index. Graphify keeps one graph per repository, and that graph is the default branch. A review analyzes the full pull request, from where it branched to its latest commit. It uses that graph to understand how the changes affect the surrounding code. See Pull request reviews. There is no setting to index every branch, or to index on every pull request. To index a different line of development, make that branch the default branch on GitHub or GitLab. Retry on a failed build indexes the current head of the default branch. One index of a repository runs at a time. A later push to the default branch waits, or joins the build already queued. Hosted plans can also limit how many push-triggered indexes a repository finishes in a UTC day. A manual reindex does not use that allowance. The allowances are on plans and pricing. The repository row can show Out of date when the newest default-branch commit is not the commit the graph is serving, and no build for that commit is running.

Follow a build

Open Builds and filter by repository or status. A build row identifies the repository, run state, and available timing or graph information.
  • For a queued or running build, use the available cancel control if you need to stop that attempt.
  • For a failed build, Retry starts indexing the repository’s current head. It does not replay the historical failed commit.
  • If no rows match, clear the filters before concluding that the repository has never built.
The first completed index makes code context available in Graphs. Wiki is generated alongside the code graph when available for the workspace.

Build states

Sync and reindex

Sync refreshes the list of repositories your GitHub or GitLab connection can see. Reindex rebuilds one repository’s graph from its default-branch head. You need permission to manage repositories in the workspace. These events never start an index: a push to a non-default branch, a branch deletion, and any push to a repository whose indexing is off.

When a rebuild is skipped

If the graph already covers the latest default-branch commit, Graphify tells you the rebuild was skipped instead of quietly returning the previous build. Typical messages:
  • Enabling indexing when the graph is already current: the repository is on, and nothing was re-indexed.
  • Reindex soon after a successful rebuild of the same commit: index_rebuild_debounced (409), with when you can try again. The graph already reflects that commit.
While a rebuild runs for an unchanged commit, the published graph stays available. More fixes are on Troubleshooting.

Usage and access

Respect the limit or provisioning message shown by the console. Hosted plans have daily push-build allowances as well as build concurrency and operational limits. Uncapped graph size on Pro and Teams does not remove those limits. See plans and pricing for hosted allowances, and the workspace’s Billing view for its plan.

Next steps

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.

Repository graphs

Explore the graph Graphify built.

Pull request reviews

Turn on graph-aware reviews.