Add end-to-end tests showing use of Repository::statuses()#1251
Conversation
Specifically how it analyses files and should be used to determine if a repo is "clean". Closes rust-lang#1145
There was a problem hiding this comment.
While I don't think this really resolve the confusion of #1145, we at least have a file can point at when confusion arises. Thanks!
| std::os::unix::fs::symlink(to, from).unwrap(); | ||
|
|
||
| #[cfg(windows)] | ||
| std::os::windows::fs::symlink_file(to, from).unwrap(); |
There was a problem hiding this comment.
On windows this requires developer mode privileges btw. If we have already done this, fine, if not, better make this skippable locally and enforced in CI.
There was a problem hiding this comment.
We don't appear to have done this already - not sure how to make it skippable locally and enforced in CI, even though I use a windows machine I do all of my development in docker containers that run linux.
There was a problem hiding this comment.
Check out Cargo: https://github.com/rust-lang/cargo/blob/9a624d6147d11b3f23507c02366071e31daea4b8/crates/cargo-test-support/src/lib.rs#L1577-L1601
though that is fine. We can leave it for future :)
Specifically how it analyses files and should be used to determine if a repo is "clean".
Closes #1145