1. 22 Jul, 2016 1 commit
  2. 21 Jul, 2016 2 commits
  3. 18 Jul, 2016 2 commits
  4. 14 Jul, 2016 2 commits
  5. 13 Jul, 2016 2 commits
  6. 12 Jul, 2016 1 commit
  7. 11 Jul, 2016 2 commits
  8. 10 Jul, 2016 4 commits
  9. 09 Jul, 2016 2 commits
  10. 03 Jul, 2016 1 commit
  11. 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
  12. 01 Jul, 2016 3 commits
  13. 30 Jun, 2016 1 commit
  14. 29 Jun, 2016 2 commits
  15. 26 Jun, 2016 1 commit
  16. 24 Jun, 2016 1 commit
  17. 21 Jun, 2016 1 commit
  18. 16 Jun, 2016 3 commits
  19. 15 Jun, 2016 2 commits
  20. 12 Jun, 2016 2 commits
  21. 10 Jun, 2016 1 commit
  22. 07 Jun, 2016 1 commit
  23. 06 Jun, 2016 1 commit
  24. 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