- Add tests and docs for any new functionality
- Format the code with rustfmt
(Install with
rustup component add rustfmt
, run withcargo fmt
) or use equivalent manual formatting. - Use meaningful commit messages. You can follow the advice in this blogpost.
Thanks for your contributions :)
cargo-embed is a so called cargo subcommand. It is a programm named cargo-embed which is installed in the users path. Thus when applying some small fixes cargo-embed you can run cargo build
and then use the executable in the target folder named cargo-embed directly. You can also use cargo install --path . to install your current checkout locally overriding what you previously had installed using cargo install cargo-embed
.
The steps are the same for cargo-embed or cargo-flash. Both use probe-rs inside and wrap it with a user friendly command line interface.
If you want to use a different version of probe-rs you can use cargo patch in your local clone of cargo-embed/ cargo-flash and set it to a specific version from Github or a local checkout of probe-rs. This is helpfull for testing patches.