1# Contributing to Vibebox
3Thanks for your interest in contributing! This guide keeps PRs small, reviewable, and consistent with the project’s
8- macOS on Apple Silicon (required for the virtualization backend)
9- Rust `1.91.1` or newer (see `Cargo.toml`)
131. Fork the repo and create a feature branch.
142. Build once to validate your toolchain:
20**Development Commands**
22- Format: `cargo fmt --all -- --check`
23- Lint: `cargo clippy --all-targets --all-features -- -D warnings`
24- Test: `cargo test --locked`
25- Build: `cargo build --locked`
29- Keep changes focused and scoped to one problem.
30- Update or add tests when behavior changes.
31- If you change user-facing behavior, update docs or help text.
32- Avoid adding heavy dependencies without a clear reason.
37- macOS version and hardware (Apple Silicon model)
38- Vibebox version (`vibebox --version`)
40- Logs from `.vibebox/cli.log`, `.vibebox/vm_root.log` and `.vibebox/vm_manager.log`
43If you believe you’ve found a security issue, please avoid public disclosure. Open a private report via GitHub Security
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list