Git-native workflow automation. Simple to use. Powerful underneath.

GitVan brings Git into your workflow system. Define workflows once, trigger them on Git events (commit, push, merge), track performance automatically. All in .ttl files that live in your repo.

The innovation: Behind the scenes, GitVan uses semantic graph technology to unlock capabilities traditional workflow systems can't provide (federated queries, reactive hooks, composable workflows). But you'll never need to learn that - it's completely hidden.

# Install globally
npm install -g gitvan

# Initialize in your project
gitvan workflow init

# Create your first workflow
cat > .gitvan/workflows/hello.ttl << 'EOF'
@prefix gh: <http://example.org/git-hooks#> .
@prefix op: <http://example.org/operations#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

gh:HelloWorld a gh:Hook ;
  rdfs:label "Hello World" ;
  op:hasPipeline [
    op:hasStep [ a op:CLIStep ; op:command "echo Hello, GitVan!" ]
  ] .
EOF

# List workflows
gitvan workflow list

# Run it
gitvan workflow run HelloWorld

Choose your starting point:

Learning by doing. Hands-on guides to get you productive in 30 minutes.

• Your first workflow (10 min)
• Multi-step workflows (15 min)
• Git hooks automation (15 min)
• Performance monitoring (10 min)

Solve specific problems. Practical recipes for common tasks.

• Add a custom workflow
• Parallelize steps
• Query workflow history
• Set up SLOs and alerts
• Compose workflows

Look things up. Complete specifications of commands, formats, and APIs.

• CLI commands (all options)
• Workflow file format (all properties)
• Step types (all available steps)
• Configuration (all settings)

Understand why. Deep knowledge about architecture and design.

• Why GitVan uses RDF (hidden)
• 80/20 core components
• RDF capabilities vs JSON/YAML
• Performance characteristics
• Security implications

6 core components, 85% value. How GitVan's innovation unlocks powerful capabilities.

Lean Six Sigma quality. Failure mode analysis showing all risks are mitigated.

Design for safety. 10 Poka-Yoke mechanisms that make failures impossible.

# Global installation (recommended)
npm install -g gitvan

# Local installation (in project)
npm install gitvan

# Or with pnpm
pnpm add -g gitvan

Requirements: Node.js 18+

What: A sequence of steps that runs on Git events or on-demand.

gh:MyWorkflow a gh:Hook ;
  rdfs:label "My Workflow" ;
  op:hasPipeline [ op:hasStep step-1 ; op:hasStep step-2 ] .

Where: .ttl files in .gitvan/workflows/

Triggers: git commit, git push, git merge, or manual (gitvan workflow run)

What: Individual tasks (run shell command, query, API call, etc.)

Types:

• CLIStep - Execute shell command
• TemplateStep - Use predefined template
• SPARQLStep - Query workflow graph
• HTTPStep - Make API request
• FileStep - Read/write files

What: Workflows trigger automatically on Git events.

gitvan hook install pre-commit MyWorkflow
# Now MyWorkflow runs before every commit

What: Automatic SLO tracking and metrics collection.

gh:Deploy a gh:Hook ;
  perf:sloTarget 300000 ;      # 5 minute target
  perf:sloP99 360000 .         # p99 under 6 minutes

See How-To Guides for detailed instructions.

@prefix gh: <http://example.org/git-hooks#> .
@prefix op: <http://example.org/operations#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

gh:LintOnCommit a gh:Hook ;
  rdfs:label "Lint on Commit" ;
  op:hasPipeline [
    op:hasStep [
      a op:CLIStep ;
      rdfs:label "Lint code" ;
      op:command "npm run lint" ;
      op:timeout 30000 ;
      op:failOn "error"
    ]
  ] .

Register:

gitvan hook install pre-commit LintOnCommit

gh:BuildAndDeploy a gh:Hook ;
  rdfs:label "Build and Deploy" ;
  op:hasPipeline [
    op:hasStep gh:build ;
    op:hasStep gh:test ;
    op:hasStep gh:deploy
  ] .

gh:build a op:CLIStep ;
  op:command "npm run build" ;
  op:timeout 60000 .

gh:test a op:CLIStep ;
  op:command "npm test" ;
  op:timeout 120000 ;
  op:dependsOn gh:build .

gh:deploy a op:CLIStep ;
  op:command "npm run deploy" ;
  op:timeout 180000 ;
  op:dependsOn gh:test .

Workflows live in your repo as .ttl files. Version them with Git, review in PRs.

Ask "Which workflows use Docker?" → One query, instant answer. JSON/YAML requires manual scanning.

Combine workflows into larger workflows without duplication.

Workflows automatically trigger based on state changes, not just Git events.

SLO tracking and performance metrics built-in from day one.

Every workflow change is immutably recorded with full provenance.

.gitvan/
├── workflows/           # Your workflow definitions (.ttl files)
│   ├── build.ttl
│   ├── test.ttl
│   ├── deploy.ttl
│   └── lint.ttl
├── config.yaml         # GitVan configuration
└── hooks/              # Git hook symlinks (auto-generated)
    ├── pre-commit
    ├── post-commit
    └── pre-push

• Tutorials - Step-by-step learning
• How-To Guides - Specific problem-solving
• Reference - Complete specifications
• Explanation - Conceptual understanding
• gitvan --help - CLI help

See 80/20 Architecture for detailed benchmarks.

✓ Immutable audit trail - Every change tracked and signed ✓ Sandboxed execution - Workflows cannot crash system ✓ Pre-execution validation - Invalid workflows caught before running ✓ Atomic transactions - All-or-nothing workflow changes ✓ Error isolation - Single bad workflow doesn't affect others ✓ Concurrent write protection - Git serializes modifications

See Poka-Yoke for 10 error-prevention mechanisms.

# Clone and install
git clone https://github.com/gitvan/gitvan.git
cd gitvan
npm install

# Run tests
npm test

# Build
npm run build

# Local CLI
node src/cli.mjs --help

MIT - See LICENSE

• GitHub: github.com/gitvan/gitvan
• npm: npmjs.com/package/gitvan
• Issues: github.com/gitvan/gitvan/issues