pip generated this folder for a few versions, as part of it's initial
implementation of PEP 517.

pip has not generated this folder for a few versions now, so it should
be OK to remove this from the standard gitignore file.

These generated files were added in https://github.com/coq/coq/pull/745

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-build.html

This reverts commit e931ef7f3e.

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

PyB 0.12 uses `$project_root/.pybuilder/` for internal venvs.

Projects using QML files generating a temporary qrc file if a qrc file present in the project.

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/.

Ignore .dirstamp files from automake used for non-existing directory dependencies.

* 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.

When using a file upload gem called Shrine, its file system mode put images under `public/uploads`.

053bcf297e/doc/storage/file_system.md

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.

Similar to #2608, it's the defacto tsc way now for adding typings locally.

Add ignore to umbraco folder as it will be added by Install-Package UmbracoCms or updated by Update-Package UmbracoCms

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.

* add alternative sftp settings file

* update for possible multiple alt* numbered files

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.

Unity 2020 introduces a new "UserSettings" top-level project folder.
See https://forum.unity.com/threads/whats-the-usersettings-directory.754436/ for more information.

pytype is a static type analyzer for Python code;
it generates files of inferred type information,
located by default in .pytype/pyi.

The project description file.

The Godot editor automatically creates those binary files from
translations in CSV format. There's no need to add them to
version control.

* 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

Add missing slash to make pattern accurate, since the JetBrains folder is always relative to root assets folder.

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.