Before you start
- An account at app.graphify.com. New accounts start on a 14-day Pro trial, then move to Free (up to 3 indexed repositories). No card is required.
- For the local commands, the open-source CLI. See Installation.
- A repository with the status Indexed, or a local graph at
graphify-out/graph.json. - For the local commands, the GitHub CLI signed in to the repository.
graphify prsreads open pull requests through it.
In Graphify
On a connected repository, Graphify checks each pull request for cross-branch conflicts with the other open pull requests and gives a merge order. It does this along with the review of each pull request. Like the review, it is advisory and doesn’t block a merge.With the local CLI
From the repository root, list the open pull requests that share a graph community:GRAPHIFY_TRIAGE_BACKEND, and optionally GRAPHIFY_TRIAGE_MODEL, to choose one.
For example, on a clone of the open-source repository:
Read the result
Pull requests in the same community change code that is closely connected in the graph. Review them together and agree an order. After each merge, rebase the others and run your tests. A pull request missing from the list can still conflict in ways the graph does not show, such as config or generated files.If something fails
Pull request context covers the rest of
graphify prs and the MCP tools for pull requests.
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.
Pull request reviews
What Graphify checks on each pull request.
Check the impact of a change
See what a change reaches before you open it.