CI Integration

rx is designed to work seamlessly in continuous integration environments. This section covers the official GitHub Action, VS Code extension, and general CI best practices.

One-command CI

The simplest way to run your full CI pipeline is:

rx ci

This executes, in order:

1. rx fmt --check – verify formatting
2. rx lint – run clippy with configured severity
3. rx test – run the test suite
4. rx build – verify the build succeeds

CI profiles

Use a profile to customize behavior for CI:

[profile.ci]
build = { cache = false, jobs = 2 }
lint = { severity = "deny" }
test = { runner = "nextest" }
env = { CI = "true", RUST_BACKTRACE = "1" }

rx --profile ci ci

Affected-only execution

In large workspaces, only check what changed (plus its dependents):

rx ci --affected --base main
rx test --affected --base main

Recommended CI pipeline

rx --profile ci ci

Or as separate steps for better CI reporting:

steps:
  - run: rx fmt --check
  - run: rx lint
  - run: rx test --affected --base main
  - run: rx build --release

Dedicated tools slot in as extra steps where you need them (e.g. cargo audit, cargo deny).

Integrations

• GitHub Action – official action for GitHub Actions
• VS Code Extension – editor integration for local development