GitHub at Avo

GitHub hosts every Avo client project in a private repository. The client gets collaborator access to their repo so they can see the full commit history, run their own audits, and take ownership of the codebase after delivery. No lock-in. The code is theirs.

The CI/CD pattern Avo uses is GitHub Actions with environment-specific deploy workflows. A merge to the main branch triggers a production deploy via Vercel (for Next.js projects) or a custom deploy script for non-Vercel targets. Pull request branches get preview deployments automatically so changes can be reviewed in a live environment before merging. Failed deploys send a Slack notification to the project channel.

The Avo platform itself (avo-site) runs this same pattern. The deployment history in Vercel ties back to the GitHub commit SHA, making it easy to trace what is live and roll back to any previous commit if needed.

For the Avo Engine build, the Rust workspace (75+ crates) lives in a single Cargo workspace repository. GitHub Actions runs cargo test --workspace and cargo clippy on every push to ensure the workspace builds and passes lint before any artifact is marked deployable. Build times on the GitHub-hosted runners are approximately four minutes for a cold full-workspace build.