GitHub-compatible CI

Workflow location

Vex CI reads GitHub Actions-style workflow definitions from .vex/workflows. Keep workflow files with the repository they validate, and treat Vex compatibility as an explicit surface rather than assuming every GitHub Actions feature is available.

Triggers and concurrency

Vex evaluates the configured workflow triggers against repository events and change lifecycle. A checkpoint workflow is opt-in through an explicit on: checkpoint: key, so an agent checkpoint does not silently trigger a bare on: push: workflow.

Use workflow concurrency and the repository queue deliberately: CI and landing remain separate stages with independent diagnostics.

Enable remote GitHub CI

When a Vex repository remains connected to GitHub, attach the GitHub App installation during the import or sync setup. This establishes the provider authority and the ability to reflect compatible checks where configured.

See import and sync for GitHub connection options and source control for Vex changes and landing.

Blocking diagnostics

Vex exposes compatibility and workflow diagnostics rather than silently accepting an unsupported configuration. Inspect checks on the change or repository surface before requesting a landing. The server continues to enforce CI, approval, queue-order, and target-freshness gates when a change is landed.