| Filename | Latest commit message | Latest commit date |
|---|---|---|
| .. | ||
| bazel.yml | ||
| blob-size-policy.yml | ||
| cargo-deny.yml | ||
| ci.yml | ||
| cla.yml | ||
| close-stale-contributor-prs.yml | ||
| codespell.yml | ||
| Dockerfile.bazel | ||
| issue-deduplicator.yml | ||
| issue-labeler.yml | ||
| README.md | ||
| rust-ci-full.yml | ||
| rust-ci.yml | ||
| rust-release-argument-comment-lint.yml | ||
| rust-release-prepare.yml | ||
| rust-release-windows.yml | ||
| rust-release-zsh.yml | ||
| rust-release.yml | ||
| rusty-v8-release.yml | ||
| sdk.yml | ||
| v8-canary.yml | ||
| zstd | ||
Workflow Strategy
The workflows in this directory are split so that pull requests get fast, review-friendly signal while main still gets the full cross-platform verification pass.
Pull Requests
bazel.ymlis the main pre-merge verification path for Rust code. It runs Bazeltestand Bazelclippyon the supported Bazel targets, including the generated Rust test binaries needed to lint inline#[cfg(test)]code.rust-ci.ymlkeeps the Cargo-native PR checks intentionally small:cargo fmt --checkcargo shearargument-comment-linton Linux, macOS, and Windowstools/argument-comment-lintpackage tests when the lint or its workflow wiring changes
Post-Merge On main
bazel.ymlalso runs on pushes tomain. This re-verifies the merged Bazel path and helps keep the BuildBuddy caches warm.rust-ci-full.ymlis the full Cargo-native verification workflow. It keeps the heavier checks off the PR path while still validating them after merge:- the full Cargo
clippymatrix - the full Cargo
nextestmatrix - release-profile Cargo builds
- cross-platform
argument-comment-lint - Linux remote-env tests
- the full Cargo
Rule Of Thumb
- If a build/test/clippy check can be expressed in Bazel, prefer putting the PR-time version in
bazel.yml. - Keep
rust-ci.ymlfast enough that it usually does not dominate PR latency. - Reserve
rust-ci-full.ymlfor heavyweight Cargo-native coverage that Bazel does not replace yet.