* Added Addressables.
Prevent automatically generated addressable files to end up in Git.
* Update .gitignore to exclude packed Addressables and Android auto-generated files.
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.
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.
In Umbraco v8 we have a new packages folder located under Umbraco/views/packages/...
This gets ignored by the current version. Adding this new line prevents this and includes all files and subfolders under this new location.
* 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.
* Update Node.gitignore
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.
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.
