You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many cargo subcommands implement a --locked flag intended to be used in CI to verify that e.g. the content of the Cargo.lock file matches that of the Cargo.toml file. Since cargo readme updates the readme based on the contents of lib.rs, it would be nice if I could have my CI do something like
cargo readme -o README.md --locked
and have cargo readme verify that the output it would generate is identical to the present readme, without updating the file but rather fail with a non-zero exit code if the output differs.
The text was updated successfully, but these errors were encountered:
Many cargo subcommands implement a
--locked
flag intended to be used in CI to verify that e.g. the content of theCargo.lock
file matches that of theCargo.toml
file. Sincecargo readme
updates the readme based on the contents oflib.rs
, it would be nice if I could have my CI do something likeand have cargo readme verify that the output it would generate is identical to the present readme, without updating the file but rather fail with a non-zero exit code if the output differs.
The text was updated successfully, but these errors were encountered: