On Windows, when PDF is opened with Acrobat Reader, one gets following output:
! I can't write on file `document.pdf'.
Please type another file name for output:
If one simply presses "Enter" to continue, the file `.pdf` is generated. Since this is a common case and `.pdf` is never used as full file name, this file should be ignored, too.
Some popular applications (for example, Phusion Passenger) leave `*.pid.lock` file(s). For example, when you type `passenger start` with simple express app listening on port 3000, it leaves the following files:
* `passenger.3000.pid` (removed when passenger stops)
* `passenger.3000.log`
* `passenger.3000.pid.lock`
While `*pid` and `*.log` are ignored, `*.pid.lock` remains unignored. Phusion Passenger is quite popular, and `*.pid.lock` file should be ignored.
If you have a Java package with `build` in it, the current version will always ignore files in that directory.
This change makes it so only the root "build" directory is ignored.
I believe that this assumes .gitignore is in the root of a project.
In some cases Qt Creator will create a CMakeLists.txt.user file with a short hash which should also be ignored. For example:
CMakeLists.txt.user.1fa15d5
I've just upgraded to ASP.NET Core RC2, and I've found that Visual
Studio is producing a file called project.fragment.lock.json. When I
delete the file it is recreated during build. Given project.lock.json is
already ignored this looks like another file to ignore.
After trying this tool for code injeciton: https://github.com/johnno1962/injectionforxcode we added it to our workflow.
Only bad side is that there's a folder included in the project that would be worth ignoring.
We had it in our .gitignore file. Just pushing the change
Many twelve-factor apps use environment variables rather than the built in Rails secrets mechanism to store secrets.
The [dotenv](https://github.com/bkeepers/dotenv) gem is widely used for this purpose and allows environment variables to be loaded from the `.env` file. However, this file should not be committed to source control.
This PR just adds the `.env` file to `.gitignore` so that these secrets aren't accidentally committed. In some rare instances, it may be required that this file is committed to source control so I've added it to the list of files that can be removed if the developer is ok with secrets being committed.
