Read about our upcoming Code of Conduct on this issue

  1. 06 Dec, 2016 1 commit
  2. 07 Oct, 2016 1 commit
    • Nick Thomas's avatar
      Add markdown cache columns to the database, but don't use them yet · af001f6c6325
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
      af001f6c6325
  3. 19 Sep, 2016 1 commit
  4. 22 Jun, 2016 2 commits
  5. 03 Jun, 2016 2 commits
  6. 01 Jun, 2016 1 commit
    • Yorick Peterse's avatar
      Refactor Participable · 8f2d80473517
      Yorick Peterse authored
      There are several changes to this module:
      
      1. The use of an explicit stack in Participable#participants
      2. Proc behaviour has been changed
      3. Batch permissions checking
      
      == Explicit Stack
      
      Participable#participants no longer uses recursion to process "self" and
      all child objects, instead it uses an Array and processes objects in
      breadth-first order. This allows us to for example create a single
      Gitlab::ReferenceExtractor instance and pass this to any Procs. Re-using
      a ReferenceExtractor removes the need for running potentially many SQL
      queries every time a Proc is called on a new object.
      
      == Proc Behaviour Changed
      
      Previously a Proc in Participable was expected to return an Array of
      User instances. This has been changed and instead it's now expected that
      a Proc modifies the Gitlab::ReferenceExtractor passed to it. The return
      value of the Proc is ignored.
      
      == Permissions Checking
      
      The method Participable#participants uses
      Ability.users_that_can_read_project to check if the returned users have
      access to the project of "self" _without_ running multiple SQL queries
      for every user.
      8f2d80473517
  7. 09 May, 2016 1 commit
  8. 11 Mar, 2016 1 commit
    • Yorick Peterse's avatar
      Use ILIKE/LIKE for searching snippets · 495c5db5b4ec
      Yorick Peterse authored
      Previously this used a regular LIKE which is case-sensitive on
      PostgreSQL. This ensures that for both PostgreSQL and MySQL the
      searching is case-insensitive similar to searching for projects.
      495c5db5b4ec
  9. 05 Mar, 2016 1 commit
  10. 09 Dec, 2015 1 commit
  11. 19 Jun, 2015 1 commit
  12. 10 Jun, 2015 1 commit
  13. 26 May, 2015 2 commits
  14. 12 Feb, 2015 1 commit
  15. 09 Oct, 2014 1 commit
  16. 26 Jun, 2014 1 commit
  17. 09 Apr, 2014 1 commit
  18. 21 Aug, 2013 1 commit
  19. 19 Jun, 2013 1 commit
  20. 24 Mar, 2013 1 commit
  21. 22 Jan, 2013 1 commit
  22. 19 Nov, 2012 1 commit
  23. 09 Oct, 2012 2 commits
  24. 26 Sep, 2012 1 commit
  25. 02 Sep, 2012 1 commit
  26. 29 Aug, 2012 2 commits
  27. 26 Jun, 2012 1 commit
  28. 27 Oct, 2011 1 commit
  29. 21 Oct, 2011 1 commit
  30. 17 Oct, 2011 1 commit
  31. 16 Oct, 2011 1 commit