Add Cargo.lock to the repository (if there exist one)

[mzji]

As per the Cargo reference, for programs, Cargo.lock should be in the repository.

[nabijaczleweli]

But this is a library

[mzji]

Wait, there is a [[bin]] section in the Cargo.toml, so it at least contains one binary... right? Edit: Most third-party cargo subcommands in the official list have a Cargo.lock in their repository, for example: cargo-tree/Cargo.lock.

[nabijaczleweli]

There's a [[bin]] exactly because it's a library.

[nabijaczleweli]

Re: edit: that's because cargo-tree isn't a library

[mzji]

cargo-edit is a library and contains a binary, its repo contains a Cargo.lock.

[nabijaczleweli]

Maybe killercup views it primarily as an exec, secondarily as a library, v0v. This is a library first, an exec second (think of the exec like an example, which it basically is (and should be)).

[mzji]

Ah, OK, so maybe Cargo.lock should be added into the .gitignore , just like Clippy

[nabijaczleweli]

It is in .gitignore

[mzji]

Ah got it. Thanks for the explain! Not very familiar with the syntax of .gitignore , almost misinterpreted.

[nabijaczleweli]

I like to use an inverted .gitignore - everything is ignored except the files specified with ! before them