/ebin can't be simply ignored because *.app should be put here.
[Erlang Applications](http://erlang.org/doc/design_principles/applications.html)
> 8.4 Directory Structure
> ebin - Contains the Erlang object code, the beam files. The .app file is also placed here.
Kevin Cunnane [Fri, 9 Sep 2016 01:09:05 +0000 (18:09 -0700)]
Ignore .jfm files in Visual Studio
.jfm files have started blocking checking for .sqlproj projects in Visual Studio. .jfm files are a new file-type created by the Microsoft ESENT database engine - this is a recent improvement only in Windows 10 Anniversary update. As the SSDT .sqlproj type in Visual Studio uses this engine for .dbmdl metadata files, and this file is locked by the user, this currently blocks users from checking into Git repositories.
This fix helps mitigate this by avoiding checkin of this file type.
Shubham Rao [Mon, 22 Aug 2016 18:06:09 +0000 (23:36 +0530)]
nbactions.xml must not be ignored (?)
This file as documentation (which seems lacking) states is used for calling custom Maven goals from the IDE.
Ignoring this file was a source much confusion in few projects (mapping Run action to custom goals... etc etc)
Also this file does anything worth ignoring
Added by #145
Exclusion of `nbactions.xml` from `.gitgnore` should be discussed.
Brennan Fee [Fri, 5 Aug 2016 05:29:32 +0000 (22:29 -0700)]
Update Visual Studio Code to support workspace files.
Visual Studio Code has a few files that can be placed into the workspace
in order to share settings across users. Settings.json is for project
specific overrides. Tasks.json is for executable tasks (build, gulp, etc.)
While launch.json is for debugging specific tasks.
Oliver Kopp [Sun, 10 Jul 2016 12:35:30 +0000 (14:35 +0200)]
Ignore .pdf
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.
Roman Pushkin [Sat, 2 Jul 2016 16:05:05 +0000 (09:05 -0700)]
Ignore *.pid.lock
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.
Mike Kobit [Fri, 24 Jun 2016 17:26:18 +0000 (12:26 -0500)]
Only ignore the build directory in the same directory as .gitignore for Gradle
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 addition to *.VC.opendb, *.VC.db file should be regenerated by Visual Studio automatically. So, it makes sense to ignore *.VC.db file too as it's been ignored in https://github.com/github/gitignore/blob/master/VisualStudio.gitignore
James Skimming [Mon, 23 May 2016 10:49:24 +0000 (11:49 +0100)]
VisualStudio ignore project.fragment.lock.json
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.
Raimon Lapuente [Fri, 13 May 2016 15:15:22 +0000 (17:15 +0200)]
Add injection folder 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
Max Woolf [Thu, 12 May 2016 07:53:20 +0000 (08:53 +0100)]
Add .env to optionally ignored files
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.
projects / gitignore.git / log