Repository indexing and sync: builds and reindex

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. 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 to inspect available controls for PR reviews, Fix suggestions, Formal verification, and Indexing. Available actions depend on the workspace’s configuration and access. The Indexing control pauses or enables indexing. Review and verification controls are separate; do not use an indexing toggle as a substitute for review configuration.

​

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. A pull request does not build a second graph. Graphify keeps one graph per repository, and that graph is the default branch. A pull request is reviewed against that graph and the pull request’s diff. 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. 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