Thanks for wanting to contribute! Here are a few guidelines to keep things smooth.
- Check the Issues page for open tasks. Issues labeled
good first issueare great starting points. - Comment on the issue you want to work on so others know it's taken.
- One issue per PR. Keep PRs focused on a single feature or fix. If you want to tackle multiple issues, open separate PRs for each.
- Link the issue. Include
Closes #<number>in your PR description so the issue gets closed automatically when merged. - Rebase on latest main. Before opening your PR, make sure your branch is up to date with
mainto avoid merge conflicts.
- Run
cargo checkbefore submitting to make sure everything compiles. - Run
cargo fmtto keep formatting consistent. - Run
cargo clippyto catch common mistakes. - If you're adding a new dependency to
Cargo.toml, explain why it's needed in the PR description.
- CI will automatically run
cargo check,cargo build, andcargo teston your PR. - If CI fails, check the logs and push a fix.
- Once reviewed and approved, your PR will be squash-merged into
main.
Open a Discussion or comment on the relevant issue. Happy hacking!