Cli command generates project to ignore Cargo.lock file
mxsm opened this issue · 4 comments
Why should we ignore Cargo.lock by default?
Why should we ignore Cargo.lock by default?
@Millione From a practical standpoint, if you're building a third-party library type of service, consider adding Cargo.lock to your .gitignore file.However, if you're developing a product intended for end-users, such as a command-line tool or application that users can run like an executable, it's a good practice to include the Cargo.lock file in your source code directory.
IMO. Letting the Cargo tool generate it automatically feels better to me.
In fact, the rust official recommendation is to include the Cargo.lock whatever your product is a library or a end-user binary.
In fact, the rust official recommendation is to include the Cargo.lock whatever your product is a library or a end-user binary.
I got it! Thank you for your answer. I will close this issue and related pr