Add Cargo.lock to gitignore #22
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tibo-lg
pushed a commit
to p2pderivatives/rust-bitcoin
that referenced
this pull request
Sep 1, 2020
Update rust-bitcoin and use bitcoin hashes new library
Davidson-Souza
pushed a commit
to Davidson-Souza/rust-bitcoin
that referenced
this pull request
Jul 12, 2023
Fix for older rustcs, removing serde/rustc-serialize and a missing include in fuzztarget
yancyribbens
pushed a commit
to yancyribbens/rust-bitcoin
that referenced
this pull request
Mar 23, 2024
Removed Ord/PartialOrd derive rules for types.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Latest cargo versions automatically add Cargo.lock to the gitignore of the generated project. Cargo.lock has metadata which dependends to the local build, so it's a good idea to ignore it in libraries. The exact rationale can be found in the following link: doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries.