Fission

CI/CD Overview for Contributors

Fission uses layered GitHub Actions workflows so pull requests get fast signal while main receives deeper validation.

Authoritative diagrams and commands live in .github/CI_CD_GUIDE.md—read that file before changing workflows.

Fast gate (ci.yml)

Runs on pull requests and pushes to main:

• Security scans (cargo deny, cargo audit, optional npm audit for Tauri)
• Formatting + clippy
• Targeted Linux tests (fission-pcode, fission-automation, fission-loader)
• Release-style builds/tests on Windows and macOS for fission-cli

Expect this gate to remain merge-blocking under branch protection.

Heavy validation (ci-heavy.yml)

Runs on main pushes, nightly schedule, and manual dispatch:

• Corpus manifest validation
• Broader workspace tests (including split fission-static coverage)
• Tauri Linux build lane
• nir-check automation with artifact uploads
• Python full-benchmark harness (per reusable workflow wiring)

Consult .github/workflows/ci-heavy.yml for exact job graphs—they evolve.

Release (cd.yml)

Tag-driven (v*.*.*) builds publish multi-platform CLI archives via softprops/action-gh-release.

Local reproduction cheatsheet

cargo fmt --all -- --check
cargo clippy --workspace --exclude fission-tauri -- -D warnings   # adjust per AGENTS.md guidance
cargo test -p fission-pcode -p fission-automation
cargo run -p fission-automation -- nir-check --lane nir

Related wiki pages

• NIR-check and CI
• PR checklist

Related repository docs

• .github/CI_CD_GUIDE.md
• .github/workflows/ci.yml

This site is open source. Improve this page.