6 releases (breaking)
Uses new Rust 2021
|0.5.0||Nov 20, 2021|
|0.4.0||Nov 16, 2021|
|0.3.0||Nov 1, 2021|
|0.2.0||Oct 31, 2021|
|0.0.0||Oct 9, 2021|
#92 in Cargo plugins
44 downloads per month
Cargo command to create your README from your crate’s documentation.
You can install cargo rdme with cargo by running
cargo install cargo-rdme.
Cargo rdme will insert your crate’s documentation in your README file. To control where the
documentation will be inserted you need to insert a marker:
<!-- cargo-rdme -->. For example,
you can start your README with some glorious badges and follow up with the rustdoc
[![Build Status](https://example.org/badge.svg)](https://example.org/link-to-ci) <!-- cargo-rdme -->
cargo rdme you will find your README to be something like:
[![Build Status](https://example.org/badge.svg)](https://example.org/link-to-ci) <!-- cargo-rdme start --> <WHATEVER-YOUR-CRATES-DOC-IS> <!-- cargo-rdme end -->
Whenever change your crate’s documentation you just need to run
cargo rdme to update your
The documentation of your crate doesn’t always map directly to a good README. For example, rust code blocks can have hidden lines. Those should not be shown in the README file.
This section covers the transformation cargo rdme automatically apply to generate a better README.
Rust code block are transformed in two ways by cargo rdme:
- Rust code blocks with lines starting with
#will be omitted, just like in
- Rust code blocks get annotated with the
rustmarkdown tag so it gets proper syntax highlighting. We also remove tags that only concern
In the table below you can see an example of these modification. The code block now is
rust and hidden lines were removed:
Currently we only support links of the form
[⋯](crate::⋯), so be sure to use that format.
Links to the standard library are also supported, and they must be of the form
<crate> is a crate that is part of the standard library, such as
Take a look at the example below:
Note that there is some limitations in intralink support. This is a complex feature: cargo rdme
needs to do some work to be able to create the link to docs.rs. This is because the link
includes the kind of item the intralink points to, in the case of
is_prime we need to discover
that is a function to generate a link that ends in
fn.is_prime.html. Therefore, intralink
support should be considered "best effort" (for instance, don’t expect items generated by macros
to be resolved). If cargo rdme is unable to generate the link it will still generate the README
file, but a warning will be emitted.
If the default behavior of
cargo rdme is not appropriate for your project you can crate a
.cargo-rdme.toml in the root of your project. This is how that
configuration file can look like:
# Override the README file path. When this is not set cargo rdme will use the file path defined # in the project’s `Cargo.toml`. readme-path = "MY-README.md" # What line terminator to use when generating the README file. This can be "lf" or "crlf". line-terminator = "lf" # If you are using a workspace to hold multiple projects, use this to select the project from # which to extract the documentation from. It can be useful to also set `readme-path` to create # the README file in the root of the project. workspace-project = "subproject" # The default entrypoint will be `src/lib.rs`. You can change that in the `entrypoint` table. [entrypoint] # The entrypoint type can be "lib" or "bin". type = "bin" # When you set type to "bin" the entrypoint default to `src/main.rs`. If you have binary targets # specified in your cargo manifest you can select them by name with `bin-name`. bin-name = "my-bin-name"
These setting can be overridden with command line flags. Run
cargo rdme --help for more
To verify that your README is up to date with your crate’s documentation you can run
cargo rdme --check. The exit code will be
0 if the README is up to date,
2 if it’s
4 if there were warnings.