rustup component add rustfmt, run with cargo fmt) or use equivalent manual formatting.Thanks for your contributions :)
To avoid conflicts in the changelog file, the changelog is assembled out of fragments at release time. To describe the changes in a PR, add a new file in changelog/. The filename should start with one of the following categories:
For example, added-ultra-fast-flashing.md would lead to an entry in the ## Added section of the changelog. The content of the file should be a single line or paragraph describing your changes.
cargo-embed is a so called cargo subcommand. It is a program named cargo-embed which is installed in the users path. Thus when applying some small fixes to 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 probe-rs-tools 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 helpful for testing patches.