1. 10 Jul, 2016 2 commits
    • Brendan Forster's avatar
      Merge pull request #2040 from koppor/patch-3 · 95ee520a
      Brendan Forster authored
      Ignore .pdf
      95ee520a
    • Oliver Kopp's avatar
      Ignore .pdf · d8a56ffd
      Oliver Kopp authored
      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.
      d8a56ffd
  2. 03 Jul, 2016 1 commit
  3. 02 Jul, 2016 1 commit
    • Roman Pushkin's avatar
      Ignore *.pid.lock · 55157bfd
      Roman Pushkin authored
      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.
      55157bfd
  4. 01 Jul, 2016 3 commits
  5. 30 Jun, 2016 1 commit
  6. 29 Jun, 2016 2 commits
  7. 26 Jun, 2016 1 commit
  8. 24 Jun, 2016 1 commit
  9. 16 Jun, 2016 3 commits
  10. 15 Jun, 2016 2 commits
  11. 12 Jun, 2016 2 commits
  12. 10 Jun, 2016 1 commit
  13. 07 Jun, 2016 1 commit
  14. 06 Jun, 2016 1 commit
  15. 23 May, 2016 1 commit
    • James Skimming's avatar
      VisualStudio ignore project.fragment.lock.json · be2df771
      James Skimming authored
      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.
      be2df771
  16. 21 May, 2016 2 commits
  17. 20 May, 2016 3 commits
  18. 18 May, 2016 3 commits
  19. 16 May, 2016 5 commits
  20. 13 May, 2016 1 commit
  21. 12 May, 2016 3 commits
    • Brendan Forster's avatar
      Merge pull request #1973 from maxehmookau/patch-1 · 9779d87d
      Brendan Forster authored
      Add .env to optionally ignored files
      9779d87d
    • Max Woolf's avatar
      Annotate .env addition · a275681e
      Max Woolf authored
      a275681e
    • Max Woolf's avatar
      Add .env to optionally ignored files · 85147407
      Max Woolf authored
      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.
      85147407