Martin von Zweigbergk 86cd0fa570 docs: touch up contributor guide, mentioning cargo nextest --workspace ... It can be confusing that the lib crate is not tested when you run `cargo test` without `--workspace` from the root directory. Also, `nextest` is a non-obvious quality-of-life improvement, so let's suggest that.		2022-12-16 22:08:17 -08:00
..
technical	docs: mention that the "view" object knows about all workspaces	2022-12-08 17:30:29 -08:00
branches.md
code-of-conduct.md
config.md
config.toml
conflicts.md	docs: indent conflict marker examples to not confuse tools	2022-12-12 16:20:40 -08:00
contributing.md	docs: touch up contributor guide, mentioning cargo nextest --workspace	2022-12-16 22:08:17 -08:00
git-comparison.md
git-compatibility.md
operation-log.md	docs: mention that the "view" object knows about all workspaces	2022-12-08 17:30:29 -08:00
related-work.md
revsets.md
tutorial.md	tutorial: mention jj edit and when it's useful	2022-12-09 22:28:33 -08:00
working-copy.md	cli: add a command for updating a stale working copy	2022-12-05 08:50:52 -08:00