Workflows
FreshOverview
Graphify fits into multiple development workflows depending on your team size and how frequently your codebase changes.
Workflow Patterns
flowchart TD
A[Start] --> B{Team Size?}
B -->|Solo| C[Solo Developer Workflow]
B -->|Team| D[Team Workflow]
C --> E{Update Frequency?}
E -->|Frequent changes| F[Watch Mode]
E -->|Milestone-based| G[Git Hook Automation]
D --> H[Shared Graph via Git]
H --> I[Git Hook on commit]Choosing a Workflow
| Workflow | Best For |
|---|---|
| Solo Developer | Individual projects, prototypes, research |
| Team Workflow | Shared codebases, multiple contributors |
| Git Automation | Any project where the graph must stay current automatically |
| Watch Mode | Active development with frequent file changes |
Core Principle
The graph is most valuable when it's current. The workflows below are designed to keep graphify-out/graph.json up to date with minimal friction.