Skip to main content
Docs drift. A function is renamed or its behavior changes, and the README, the runbook and the design doc still describe the old version. Graphify connects docs to the code they mention, so a pull request can flag the docs it may have made stale. This walkthrough uses the open-source Graphify-Labs/graphify repository, whose docs sit next to its code.

​
Walk through it

1

Index the repository

Connect it on Repositories and wait for Indexed. See Index your first repository and Repositories and builds.
2

Turn on stale-docs checks

On Repositories, open Options for the repository and check that Stale docs is on. It is on unless someone turned it off.
3

Change some code

Open a pull request that renames or changes a function the docs mention. The review can include Docs that may be stale (advisory), listing docs that mention the code you changed. See Pull request reviews.
4

Bring in docs outside the repository

Connect a Google Drive folder so your workspace and agents can search those documents next to your code. See Connect Google Drive.
The list is a prompt to check, not a verdict. A doc can mention a function without describing the part that changed. The Wiki is generated alongside the code graph, so it follows each index of the default branch.

​
Do it locally instead

Keep the local graph current as you work, so your assistant reads docs and code from the same state:
The hooks refresh the graph after commits and branch switches. Run graphify update . after a pull or a merge. Docs and PDFs go through a semantic pass with your assistant’s model or a configured backend, such as a local Ollama. See Keep the graph current.

​
Next steps

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.