I love cargo-watch, and use it on everything! Right now, I am having a bit of trouble figuring out how to ignore a file properly.

The following invocations successfully ignore README.md:

• cargo watch -w src -s "touch README.md"
• cargo watch -i '.md' -s "touch README.md"
• cargo watch -i '*.md' -s "touch README.md"

The following invocations don't ignore README.md, which means

A deny.toml without an [advisories] section will still check the RustSec when running cargo deny check advisories. This is great and the correct behaviour imo, but it would be good to document the default value for all configuration option and afaict it is not.

Thanks! :)

This is a tracking issue for additional Store implementations.

Here is a non-exhaustive list of potential candidates for an Store implementation:

• S3Storage:
  This would store crate tarballs and rendered README pages into Amazon's S3.
• RemoteStorage:
  Requires to implement a companion server.
  The idea is to have a reserved folder on another machine which runs a comp

Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what cargo does. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.

Optional dependencies can be displayed with a dashed line.