Skip to content

chore: adopt vigOS convention + mat-rs PR gate#7

Merged
gerchowl merged 1 commit intodevfrom
chore/bootstrap-vigos-convention
Apr 15, 2026
Merged

chore: adopt vigOS convention + mat-rs PR gate#7
gerchowl merged 1 commit intodevfrom
chore/bootstrap-vigos-convention

Conversation

@gerchowl
Copy link
Copy Markdown
Contributor

Summary

First PR under the new dev/main rulesets. Bundles four housekeeping items and the new Rust PR gate.

Commits:

  • chore: housekeeping — sync mat-rs/Cargo.lock to v0.2.0 release, bump .vig-os devcontainer 0.3.0 → 0.3.3, gitignore .cursor/
  • ci(rust): add PR gate for mat-rs crate — cargo fmt/clippy/test on pull_request

Context

  • Branch rulesets were just applied to main and dev (see #522 on vig-os/devcontainer for the gap in the scaffold docs).
  • The mat-rs crate previously had no PR-time CI gate — release-rs-materials.yml only runs on tag push, so a broken Rust change could land undetected. This PR closes that gap.
  • The Rust (mat-rs) check will be added to the required-status-checks list in both rulesets after this PR confirms the context name.

Test plan

  • Lint & Format passes
  • Tests pass
  • Security Scan passes
  • Dependency Review passes
  • CodeQL Analysis (python) passes
  • Rust (mat-rs) — cargo fmt --check, cargo clippy -D warnings, cargo test all pass
  • CI Summary green

🤖 Generated with Claude Code

- .vig-os: bump DEVCONTAINER_VERSION 0.3.0 → 0.3.3 (latest)
- ci.yml: add Rust (mat-rs) job running cargo fmt --check +
  clippy -D warnings + cargo test on every pull_request.
  Previously the crate only ran in release-rs-materials.yml
  on tag push, so broken Rust changes could land undetected.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gerchowl gerchowl force-pushed the chore/bootstrap-vigos-convention branch from 5efb0c8 to bc8213c Compare April 15, 2026 08:30
@gerchowl gerchowl merged commit 56137fc into dev Apr 15, 2026
12 checks passed
@gerchowl gerchowl deleted the chore/bootstrap-vigos-convention branch April 15, 2026 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant