graphify v0.5.0 — clone any GitHub repo, cross-repo graphs, and data-loss protection #528
safishamsi
announced in
Announcements
Replies: 1 comment
-
|
Does |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone 👋
v0.5.0 is out on PyPI.
What's new
Clone any GitHub repo directly
Clones to
~/.graphify/repos/karpathy/nanoGPT, runs the full pipeline on it. Repeat calls justgit pull. Supports--branchand--out.Cross-repo knowledge graphs
Run graphify on two repos, then merge their graphs into one:
Every node carries a
repotag so you can filter by origin. Useful for mapping dependencies across microservices or understanding how two projects relate.Data-loss protection on
--updategraphify now refuses to overwrite
graph.jsonwith a smaller graph — you get a clear warning instead of silent data loss. Newbuild_merge()library function for safe incremental updates that only ever grows the graph.Duplicate node deduplication
Parallel semantic subagents sometimes produced duplicate nodes for the same entity (
achille_varziandachille_varzi_c4). The subagent prompt now blocks chunk-suffix contamination at the source, and a post-merge deduplication pass catches any stragglers.Bug fixes
CLAUDE_CONFIG_DIRenv var now respected on install (Issue: do not respect CLAUDE_CONFIG_DIR #527)graphify-out/excluded from source scanning — own output no longer triggers false incremental refresh (detect_incremental() treats generated graphify-out docs as source input and creates false semantic-refresh pressure #524)As always, open issues or drop questions in Q&A. Appreciate everyone who filed detailed bug reports — #479 and #451 especially.
Beta Was this translation helpful? Give feedback.
All reactions