Martin von Zweigbergk 8ce099470b cargo: explicitly indicate paths to publish ... Running `cargo publish` from a non-colocated repo (such as my usual repo) is currently quite scary because it uploads all non-hidden files, even if they're ignored by `.gitignore` (https://github.com/rust-lang/cargo/issues/2063). I noticed this a while ago and have always run the command from a fresh clone since then. To avoid the need for that, let's use the workaround mentioned on the bug, which is to explicitly list patterns we want to publish.		2024-04-15 20:37:00 -07:00
..
benches
gen-protos
proc-macros	cargo: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
src	matchers: turn RepoPathTree into generic map-like type	2024-04-16 10:10:09 +09:00
tests	git: on fetch, pin visible untracked remote refs	2024-04-14 11:38:21 +09:00
testutils	compile integration tests as a single binary	2024-02-06 18:19:41 -08:00
Cargo.toml	cargo: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
LICENSE