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 Cloud. Use Connect GitHub or Connect GitLab, then complete the provider’s repository-access flow. 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.

​
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.

​
Usage and access

Respect the limit or provisioning message shown by the console. Build concurrency and operational limits can apply even when a plan has no monthly or daily plan cap. See current pricing for hosted allowances, and the workspace’s Billing view for its plan.