jyn

Some preliminary things can be done without switching completely: - storing the current commit in the database is pretty easy - we can implement the webhook endpoint in _addition_ to...

> last visited commit I don't think this makes sense in the context on web-hooks because we might not receive the hooks in the order the crates were released. If...

Why does this need to be a new feature instead of just using `features = ["..."]`? It seems weird to have both a way to say "these exact features" and...

hmm, that didn't work for me. ``` ; llvm-cov show --instr-profile=/Users/jyn/src/inventory/fuzz/coverage/my_fuzz_target/coverage.profdata --format=html -Xdemangler=rustfilt /Users/jyn/.local/lib/cargo/target/aarch64-apple-darwin/release/my_fuzz_target error: Failed to load coverage: '/Users/jyn/.local/lib/cargo/target/aarch64-apple-darwin/release/my_fuzz_target': No coverage data found ; file /Users/jyn/.local/lib/cargo/target/aarch64-apple-darwin/release/my_fuzz_target /Users/jyn/.local/lib/cargo/target/aarch64-apple-darwin/release/my_fuzz_target: Mach-O 64-bit...

https://github.com/rust-lang/docs.rs/issues/1588#issuecomment-1464958351 has a lot of things that are very similar but not the same; I'd love to have a plan for how this affects links to transitive dependencies as well.

I'll open an issue

https://github.com/rust-lang/docs.rs/issues/1011

> Sourcegraph announced they have all crates indexed as of July this year Does that include all crates on crates.io? Or only crates that already have a public git repository?

🤷 I don't have a strong objection to that, but I think it will be a rare feature on top of a rare feature, people already mostly use the rustdoc...

sounds good to me :)