Unlike other packages, TextMesh Pro is not entirely managed by Unity's new Package Manager, and still imports some assets directly into the project.

This new file type can be generated by GHC 8.8.

https://www.haskell.org/ghc/blog/20190626-HIEFiles.html

If you have the [Ionide](http://ionide.io/) tools installed you will get an `.ionide` directory created in each directory that you open with VS Code, regardless of whether or not you are using F#.

The xy package generates *.xyd files whenever the commands

    \MakeOutlines
    \OnlyOutlines
    \ShowOutlines
    \NoOutlines

are present in the LaTeX source. These automatically-generated files
contain the dimensions of figures typeset with xy and are recreated as
needed. This is documented on pp. 15f. of the XY-pic Reference Manual
(1999/02/16).

As automatically-generated, temporary files, they should be ignored.

also, re-ordered some elements to ensure the gitignore is in directory/file and lexicographic order

This reverts commit 6ffcee97.

See also 15e56afe introduced this for Rails.gitignore.

Docs on Sqlite temporary files
https://www.sqlite.org/tempfiles.html#rollback_journals

Thanks @nickittynack (Nick Reynolds)

package not interfere with makeindex's style files

from vim's documentation on `:mksession` (:help :mksession):

 ...

 10. If a file exists with the same name as the Session file, but ending
     in "x.vim" (for eXtra), executes that as well.  You can use *x.vim
     files to specify additional settings and actions associated with a
     given Session, such as creating menu items in the GUI version.

we already have Session.vim ignored.  the Sessionx.vim file, like
Session.vim, is a user file.  a user would generally want that file kept
private or for themselves, and the public or a team fetching from or
sharing the repository generally have no interest in a file relevant
only to a particular user.  so it's a good idea to get git to help us
avoid mistakenly sharing the file.

Actually, the log generated by debug mode is *.log
i.e. ubuntu-xenial-16.04-cloudimg-console.log

When IntelliJ project is created as a file-based (i.e. without `.idea` folder, but with `.iws`, `.iml` and `.ipr` files), and this is a Gradle or Maven project with auto-import, should ignore them as well for the same reason we ignore `.idea` folder content in that case.

* ignore all caches

* ignore release folder

... to let the file point to its canonical source

* Update Node.gitignore

* Fix coverage.lcov to *.lcov

See https://lists.launchpad.net/kicad-developers/msg38339.html and https://lists.launchpad.net/kicad-developers/msg38638.html

When a Unity project is opened in Jetbrains Rider, it installs a editor plugin into the Assets/Plugins/Editor/Jetbrains folder to manage Unity->Rider integration. This plugins life cycle is managed by your local Rider install and is automatically updated by Rider. It should not be committed to source control.  This is documented by Jetbrains here https://www.jetbrains.com/help/rider/Unity.html

This change should ignore both the Jetbrains plugin folder and its .meta file correctly. For completeness, it would be nice to also ignore the /.idea*/ settings folder that Rider autogenerates, but i see a PR implementing that change has already been rejected.

The curly apostrophe in the comment is causing AWS EB CLI to fail. https://stackoverflow.com/a/55988700/594211

As described in commit c5a2ea1dd8b8f85f7524bbdaa17844f2324d02c5 in the
kicad repository itself, the fp-info-cache file should not be checked
in to version control.

(See https://git.launchpad.net/kicad/commit/?id=c5a2ea1dd8b8f85f7524bbdaa17844f2324d02c5)

This is to ignore the new Nuget Symbol Packages, which are now the recommended approach for debug symbols of public NuGet packages.
https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg

.ist files are makeindex style files, which determine how a
makeindex-generated index will look like. Therefore, they must be
included in source control.

ignore knitr and R markdown default cache directories in subdirectories

* gitignore for JENKINS_HOME Jenkins settings

This allows an admin to use git to keep a backup of Jenkins settings
without tracking binary artifacts.  Useful for preserving settings during
plugin upgrades.

Note: secret.key is purposefully not tracked by git.  This should be
backed up separately because configs may contain secrets which were
encrypted using the secret.key.

See also:

* http://jenkins-ci.org/
* https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins

* Add a few entries to Jenkins gitignore