I added this .gitignore to a project that included a file named CoverageSearchModel.cs, and the file was wrongly ignored. This change fixes the incorrect use of the range operator on the Coverlet rules.
John Stilley [Fri, 3 Jul 2020 18:07:44 +0000 (14:07 -0400)]
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
Jon Layton [Thu, 14 May 2020 11:49:06 +0000 (07:49 -0400)]
Add .yarn/install-state.gz to Node.gitignore (#3407)
After running `yarn set version berry` and `yarn install`, the file `.yarn/install-state.gz` is created.
The documentation at https://yarnpkg.com/advanced/qa#which-files-should-be-gitignored mentions that this file should be ignored:
> .yarn/install-state.tgz is an optimization file that you shouldn't have to ever commit. It simply stores the exact state of your project so that the next commands can boot without having to resolve your workspaces again.
The documentation has a minor error; the generated file is `.gz` instead of `.tgz` (source: https://github.com/yarnpkg/berry/pull/998/files#diff-23dd4c2e823c25186f1107e88e962032R201)
This will add support for the default location the Local History extension for Visual Studio Code uses.
See https://marketplace.visualstudio.com/items?itemName=xyz.local-history
Jeffrey Walton [Thu, 12 Mar 2020 11:21:54 +0000 (07:21 -0400)]
Add Win32/ to gitginore list (#3308)
Visual Studio .Net used Win32/ as one of the default output directories for C and C++ projects. Later, when 64-bit support was added to the toolchain (circa 2005), x64/ was used. The Gitignore files include x64/, but not Win32/. The commit adds support for both Win32/ and x64/.
Sam Gleske [Wed, 11 Mar 2020 13:03:44 +0000 (09:03 -0400)]
Improved JENKINS_HOME example (#3332)
After years of use I've come up with some improvements to the
`JENKINS_HOME.gitignore` example.
- Major performance improvement: On very large Jenkins installations that
have been running for more than one year, there tends to be many builds
(hundreds of thousands of builds). The `builds` directory of these
jobs contain millions of files which would cause Git to hang for
several minutes on simple commands like `git status` and longer for
committing changes. `strace` was used on Git to figure out the
performance impact and this proposed change includes the optimization.
I also added a clear comment explaining the line's purpose.
- There's an example for how to include Jenkins encryption keys, and
there's a disclaimer informing the user why they shouldn't but still
giving an example.
- Comments have been reworded and slightly reformatted to be a little
more clear.
Cython extension modules built with `gdb_debug=True` spit out debug symbols in the `cython_debug` directory at the top level of the project. The files in this directory contain hardcoded paths and are not shareable/meaningful across environments, so I think it makes sense to include them in a default Python .gitignore.
bitbonk [Fri, 28 Feb 2020 12:30:29 +0000 (13:30 +0100)]
Include Rider as a supported IDE (#3323)
AS far as I can tell this .gitignore also applies to Rider. Looking at the somewhat official .gitignore for Rider [here](https://github.com/JetBrains/resharper-rider-samples/blob/master/.gitignore), it seems compatible.
Since October 2019, Raku is the name of the language formerly known as
Perl 6. This reflects the change. It's the same language, so changes
are mostly cosmetic.
Daniel Heim [Sun, 9 Feb 2020 22:34:10 +0000 (09:34 +1100)]
Update Unity.gitignore (#3297)
Unity 2020 introduces a new "UserSettings" top-level project folder.
See https://forum.unity.com/threads/whats-the-usersettings-directory.754436/ for more information.
Simon Siefke [Mon, 16 Dec 2019 13:17:17 +0000 (14:17 +0100)]
Ignore files inside `.vscode-test` (#3256)
* Ignore files inside `.vscode-test`
[vscode-test](https://github.com/microsoft/vscode-test) is a testing framework for vscode extensions. Inside the `vscode-test` folder are stored one or more versions of vscode, which are used for testing a vscode extension.
davidkron [Fri, 6 Dec 2019 10:08:39 +0000 (11:08 +0100)]
Added jarRepositories.xml as an optional ignore (#3254)
Since IntelliJ 2019.3 this file appeared in our git changes. It seems these are just cached information about remote repositories that are defined in Maven/Gradle.
davidkron [Sun, 17 Nov 2019 18:12:38 +0000 (19:12 +0100)]
exclude compiler.xml and artifacts when using Gradle (#3236)
In our IntelliJ projects where we are using Gradle, the file .idea/compiler.xml and files inside the .idea/artifacts folder are automatically generated by IntelliJ based on the Gradle build model. As these files are generated, they should be ignored in version control.
Aikhjarto [Fri, 8 Nov 2019 21:12:40 +0000 (22:12 +0100)]
exclude *.tps files from TeXnicCenter (#3213)
TeXnicCenter produces a status file named *.tps which holds information on currently open *.tex files and window positions. This most likely should not be checked in.
Having `release/` in an Android project gitignore means those apps which have different
build types files for `debug` and `release` will fall into this
and all `release` related files will be never added or will be removed from
repository at some point.
Wes Dean [Tue, 10 Sep 2019 14:07:52 +0000 (10:07 -0400)]
Add OpenSSL-related file extensions (#3168)
There are a number of OpenSSL-related file extensions (e.g., .pem, .crt,
etc..) that contain data that are generally best not committed to
repositories. This file contains several common file extensions that
often correlate to these types of files.