Martin von Zweigbergk ce094c618b repo: propagate error when current working-copy commit is not found ... This should fix the panic in the case reported in #1107. It's a bit hard to reproduce because we normally notice the missing commit when we snapshot the working copy, but it's possible to reproduce it using `--no-commit-working-copy`. I suspect the added test is too brittle because it checks the exact error message. On the other hand, it might be useful to have one test case like this so we catch accidental changes in the format.		2023-01-24 12:20:28 -08:00
..
gen-protos	cargo: bump prost-build from 0.11.5 to 0.11.6	2023-01-13 21:24:02 +00:00
src	repo: propagate error when current working-copy commit is not found	2023-01-24 12:20:28 -08:00
tests	op_heads_store: remove LockedOpHeads	2023-01-20 15:18:08 -08:00
testutils	cargo: bump git2 from 0.16.0 to 0.16.1	2023-01-21 00:05:57 +00:00
build.rs	lib: replace protobuf crate with prost	2022-12-22 07:04:35 -08:00
Cargo.toml	cargo: bump pest from 2.5.3 to 2.5.4	2023-01-24 16:50:17 +01:00