CI Pipeline

[Maladus]

Hello

Thanks for your work.

I try to setup the Pipeline for automatically build and test the Changes on the code.
Like you mention in CONTRIBUTENG.md.

cargo check
cargo build
cargo test
cargo clippy

I test it on my personal PR (Maladus#1)

Should i open an PR or you prefers to setup CI by you own?

[sbeardsley]

Triage: confirmed gap — PR welcome! (severity: medium)

Confirmed: .github/ currently has only dependabot.yml; there are no workflows at all, so PRs get no automated verification. Given the active inbound PR traffic, this is worth closing quickly.

@Maladus — yes, please open the PR from your fork. A few notes for whoever implements it:

• The gate is already prescribed in CONTRIBUTING.md: cargo build, cargo test, cargo clippy, cargo check.
• The crate uses edition = "2024", so it needs stable Rust ≥ 1.85 (no rust-toolchain.toml is pinned currently).
• The apple-container workspace member is macOS-target-gated behind an opt-in apple feature (not default), so a standard ubuntu-latest job excludes it automatically. An optional macos-latest job with --features apple would give full coverage (note it needs protoc — brew install protobuf).

A single standard rust.yml (checkout, toolchain with clippy component, cache, the four cargo commands) covers it. Effort: small, no blockers.

[Maladus]

Opened PR #23 (Maladus:Maladus/CI → main).

Single ubuntu-latest job running the four commands from CONTRIBUTING.md (cargo check, cargo build, cargo test, cargo clippy) in a file named rust.yml per the suggestion in the triage comment. The macos-latest + --features apple job is left as a follow-up since it was marked optional.

End-to-end tested on my fork in Maladus#1 — all four steps green.