* Add more standard ignored files for Julia

In particular, this adds documentation build artifacts generated by Documenter.jl as well as Manifest.toml, which can appear in docs/, in test/, or at the top level.

* Clarify the intent of each ignored item

Also add a few more build artifacts from BinaryProvider/BinDeps.

https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/
Rails `5.2.2.1` requires `tmp` directory committed to git repository for CI to run successfully.

Visual Studio can also generate .appxbundle and .appxupload files for Windows Store apps.
See: https://docs.microsoft.com/en-us/windows/uwp/packaging/packaging-uwp-apps#types-of-app-packages

Lerna is an increasingly popular tool within node ecosystem to manage package dependencies and having writes to a `lerna-debug.log` following the yarn and npm precedence when error is encoutered.

* Update VisualStudio.gitignore file

Rider has its own ignore file, so does Visual Studio. The ignore statements for Rider (idea) IDE should be removed from Visual Studio .gitignore file template.

* Add ignore rules for Pipenv

Pipenv uses Pipfile.lock to maintain Python package information
(metadata, hash, etc.) installed as described in Pipfile. Thus,
Pipfile.lock may vary on different operating systems, platforms
when collaborating. This PR adds Pipfile.lock into the Python
default gitignore. See http://pipenv.org

* Update Python.gitignore

Not to ignore Pipfile.lock in default, but explain
when and why it should be ignored in case of
collaboration. (adjusted according to comment
in github/gitignore#2977 by @drothmaler )

* Apply suggestions from code review

Co-Authored-By: JarryShaw <jarryshaw@icloud.com>

* Update Python.gitignore

As suggested by @shiftkey , elaborate on the problems that users might see with `Pipfile.lock`.

* [Node] Ignore diagnostic report files

* Add documentation URL

* Stricter regex

R: ignore user-specific files

Migration backup

Merged down master github gitignore

Update VisualStudio.gitignore

Ignore backup files from editing reports

Add *.creator.user* files to the Qt .gitignore

[Codesniffer] remove duplicate Composer rule

Remove trailing whitespace added last commit.

Android.gitignore: Add build_file_checksums.ser and modules.xml files

Add compilation db to Qt gitignore

Add pip-wheel-metadata to Python.gitignore

PEP-517 has resulted in some updates to the Python
build process. As a result, a new directory called
pip-wheel-metadata is created on fresh builds.
This PR adds this directory into the Python default
gitignore. See
e5f4bbb7dd/src/pip/_internal/req/req_install.py (L568)

Ignore CMake FetchContent directory

CMake's `FetchContent` module creates a `_deps` directory on the root (configurable by modifying `FETCHCONTENT_BASE_DIR`)

Unity: Never ignore asset meta data

Update Ruby.ignore to ignore .byebug_history file

The file `.byebug_history` is generated when using the popular https://github.com/deivid-rodriguez/byebug gem for debugging in Ruby. It contains a list of commands the user has run while debugging, which should not be committed to the repository. The author of the gem agrees with this here: https://github.com/deivid-rodriguez/byebug/issues/204#issuecomment-178238302

I have copied this from the Rails gitignore here: f908e51bcf/Rails.gitignore (L45)

QtCreator above 4.8 version is utilizing a so called "compilation database" which placed in the compile_commands.json and contains generated information.

ignore android lint temp files.

Signed-off-by: Yousha <Yousha.A@Hotmail.com>

Unity: ignore mdbs, fix path to crashlytics file, make AssetStoreTools optional

Only people building Unity plugins will need to import the asset store tools plugin into their project, and it's a toss up whether they want to commit the tooling into their repo (they might or they might not want to, it highly depends on their workflow). The default .gitignore shouldn't be making this choice for these users.

Unity projects targeting the 2.0/3.5 runtime or built with mono < v5.0 generate `mdb` files, not `pdb` files.

Looks like the `crashlytics-build.properties` gets around in more than just the `StreamingAssets` folder, looking at [examples around the internets](https://github.com/auth0/sharelock-android/blob/master/app/src/main/assets/crashlytics-build.properties), so it should probably just be ignored as a filename.

Add version control ignore

google-services.json