Update JetBrains.gitignore

[Objective-C] Remove global rule

[ChefCookbook] Remove global rules and lockfiles

Merge RubyMotion into Ruby

Ignore coverage results from coverage.py

[VisualStudio] Remove Windows OS rules

Remove a trailing asterisk for stylistic consistency

coverage.py creates HTML reports in the htmlcov directory (this tool can also be used with coveralls.io)
http://nedbatchelder.com/code/coverage/
https://pypi.python.org/pypi/coverage

Rename IgnorePackages back to VisualStudio.gitignore.

Fix comments in Dart template

Remove overly-permissive data file rules from Node template

.gitignore uses `#` for comments, not `//`

These aren't really common patterns in the Node world, and if a Node project includes one of these types as files, they're as likely to want to include them in the project as not (`*.csv` is as likely to be a data source as `*.json`).

Refactor Node.gitignore with comments

Conflicts:
	Node.gitignore

Enable Ignore of NuGet Packages Folder By Default

Adding a global template for EiffelStudio

Simplify sass cache rules

Added rule for directory config under KDE to Linux template

Dolphin, the KDE file manager, writes specific directory configuration in .directory files.

Add an Idris template

Update Leiningen.gitignore with checkouts and lein-failures rules

Fix typo in Haskell template

Ignore signed pom files in leiningen projects

Ignore log of applied patches in Magento.gitignore

Submitting this for consideration.

The first thing that I do on every new project is to go in and uncomment the packages folder. With the prevalence of NuGet and prominence of its use in the Visual Studio environment, along with how well package restore *just works* now, I believe this should be the default.

While I understand that package restore isn't on by default, I would argue that the types of developers using NuGet _and_ a distributed SCM are the types of developers that would omit the binaries from source control.

Magento keeps a log of official patches applied in this file.

Pom files are commonly signed before deploy as part of the build/signoff process