gitignore/Rust.gitignore

# Generated by Cargo
# will have compiled files and executables
debug/
target/

# If this is a library or crate (that other Rust projects will depend upon), keep Cargo.lock in your .gitignore.
# If you’re building a binary or system library with crate-type of staticlib or cdylib, remove Cargo.lock from your .gitignore.
# If you're curious about why that is, see "Why do binaries have Cargo.lock in version control, but not libraries?" in the FAQ.
# https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
Cargo.lock

# These are backup files generated by rustfmt
**/*.rs.bk
-												add /target/ (generated by Cargo) to Rust gitignore
											
										
										
											2014-07-08 19:41:13 +02:00
+								# Generated by Cargo
-												Update Rust.gitignore

no need to specifically ignore compiled files and executables
as it will be under the target directory
											
										
										
											2016-04-15 04:14:14 +02:00
+								# will have compiled files and executables
-												Fixing target and adding debug to Rust gitignore (#3436)

The problem here was two fold:
1. the folder "/target/" would be top-level of the repo only, it should be "target/" to properly exclude target folders anywhere in the repo
2. the default Rust/Cargo folder when compiling code is "debug/", which gets used perhaps more often that "target/", added that
											
										
										
											2020-07-03 20:07:44 +02:00
+								debug/
 								target/
-												added comment
											
										
										
											2015-11-13 17:17:04 +01:00
-												Improve the guidance on Cargo.lock in Rust.gitignore

See the following for more information:
 - https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
 - https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
											
										
										
											2020-07-16 20:35:56 +02:00
+								# If this is a library or crate (that other Rust projects will depend upon), keep Cargo.lock in your .gitignore.
 								# If you’re building a binary or system library with crate-type of staticlib or cdylib, remove Cargo.lock from your .gitignore.
 								# If you're curious about why that is, see "Why do binaries have Cargo.lock in version control, but not libraries?" in the FAQ.
 								# https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
-												add Cargo.lock to gitignore file by default

See the [official recommendation](http://doc.crates.io/guide.html#cargotoml-vs-cargolock) 

> * If you're building a library, put Cargo.lock in your .gitignore.
> * If you're building an executable, check Cargo.lock into git.
											
										
										
											2015-11-13 12:05:10 +01:00
+								Cargo.lock
-												Add rustfmt gitignore (#2108)


											
										
										
											2016-10-03 05:46:39 +02:00
 								# These are backup files generated by rustfmt
 								**/*.rs.bk