Skip to main content
Push your code and the graph follows. Once a repository is connected, Graphify keeps its graph in step with your default branch. There’s nothing to install and nothing to run.

On every push

A push to the default branch starts a new build through the Graphify GitHub App.

Only what changed

Graphify re-processes the changed files and keeps the code around them in context.

Default branch only

Pushes to other branches don’t change the graph.

​
What happens when you push

1

You push to the default branch

GitHub sends the push to Graphify through the GitHub App you installed when you connected the repository.
2

Graphify works out what changed

It checks the push is for the default branch of a connected, enabled repository, then starts a build for the new head commit.
3

Only the changed files are rebuilt

The changed files are re-processed, while related code nearby stays in context, so calls and dependencies across files stay accurate.

​
What doesn’t trigger a build

Feature branches are ignored. The graph reflects your default branch, so work on a branch shows up once it’s merged.
A push that deletes a branch is ignored.
If a repository is disabled in your workspace, its pushes are skipped until you turn it back on.
Automatic builds are capped per repository each day. A push over the cap is still recorded, but no build runs for it. See push allowance.

​
Sync and reindex

Sync

Sync on the Repositories and Overview pages re-reads which repositories your GitHub connection can see. It doesn’t rebuild a graph.

Reindex

Reindex rebuilds one repository’s graph from its default-branch head, if you ever need a fresh start.

​
Using Graphify CLI instead

Keep your code graph up to date

Working locally with Graphify CLI? Use git hooks or graphify watch to refresh the graph as you commit and save.