vortex
vortex-data/vortex/.github/AGENTS.md
Prefer stable Rust for CI workflows. Only use nightly when a feature genuinely requires it. Nightly is required for: - cargo fmt (nightly formatting options) - -Z flags: sanitizers (-Zsanitizer=address), miri (-Zmiri-*), publish (-Zpublish-timeout) - cargo-fuzz (requires nightly) Everything else (build, clippy, tests, docs, benchmarks, packaging) should use stable. Nightly Rust toolchain is pinned via NIGHTLYTOOLCHAIN env var in each workflow file — update all instances when changing the version. For action inputs: toolchain: ${{ env.NIGHTLYTOOLCHAIN }} For shell commands:…
Prefer stable Rust for CI workflows. Only use nightly when a feature genuinely requires it.
Nightly is required for:
- `cargo fmt` (nightly formatting options)
- `-Z` flags: sanitizers (`-Zsanitizer=address`), miri (`-Zmiri-*`), publish (`-Zpublish-timeout`)
- `cargo-fuzz` (requires nightly)
Everything else (build, clippy, tests, docs, benchmarks, packaging) should use stable.
Nightly Rust toolchain is pinned via `NIGHTLY_TOOLCHAIN` env var in each workflow file — update all instances when changing the version.
For action inputs: `toolchain: ${{ env.NIGHTLY_TOOLCHAIN }}`
For shell commands: `cargo +$NIGHTLY_TOOLCHAIN ...`
All files under `.github/` are linted by `yamllint --strict -c .yamllint.yaml`.
More agent context in vortex-data/vortex
8 other files this repository gives its agents.
AGENTS.md
Skill
- bench-performance.agents/skills/bench-performance/SKILL.md
- ci-failure-analysis.agents/skills/ci-failure-analysis/SKILL.md
- samply.agents/skills/samply/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.