Pipelines & automation

This page is a routing guide for step/pipeline-style workflows (automation, reproducibility, CI-friendly runs).

What you should do next

• Quickstart: Getting Started (make-first)
• Pipeline tutorial: Pipeline mini-project
• CI entrypoint (projects): CI & automation
• CI entrypoint (contributors): CI & automation (repository)
• Tooling workflow:
  • Testing
  • Formatting
  • LSP
• Language foundations for “structured automation”:
  • Error Handling
  • Imports & Modules
  • File I/O

What to look for

• Deterministic commands and outputs (exit codes, reproducible runs)
• Honest “what exists today” vs “future” labeling (no implied platform integrations)

Works today (use this for pipelines)

• incan fmt --check for CI formatting enforcement
• incan test with basic filtering (-k) and CI-friendly exit codes
• incan run for deterministic single-program runs (exit code follows the program)

If you are contributing to the Incan repository itself, the CI entrypoints are make check / make test / make smoke-test (see: CI & automation (repository)).

Not yet / planned (don’t rely on it for automation)

• Project config + lockfiles (incan.toml, dependency pinning, reproducible dependency resolution)
• First-class “project lifecycle” commands (incan init/new/doctor)
• Offline/locked build workflows built into the CLI (enterprise constraints)