Yesterday I became curious about whether or not the Cargo.lock file should be included in a repo. After some reading, I know now that it should be included for binary projects / applications but not for libraries.
I'll make a PR for this once the two open PR's have been merged.
Yesterday I became curious about whether or not the `Cargo.lock` file should be included in a repo. After some reading, I know now that it _should_ be included for binary projects / applications but _not_ for libraries.
There's a great summary here: [Why do binaries have Cargo.lock in version control, but not libraries?](https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries)
I'll make a PR for this once the two open PR's have been merged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Yesterday I became curious about whether or not the
Cargo.lockfile should be included in a repo. After some reading, I know now that it should be included for binary projects / applications but not for libraries.There's a great summary here: Why do binaries have Cargo.lock in version control, but not libraries?
I'll make a PR for this once the two open PR's have been merged.
Addressed in #48