1. 21 Feb, 2019 1 commit
  2. 18 Jan, 2019 1 commit
    • Sean McGivern's avatar
      Don't check confidential issues for spam · d00b4a2e
      Sean McGivern authored
      Spam checks are meant for content that could be indexed by search
      engines. Confidential issues aren't indexed by search engines, so we
      don't need to do spam checks for them.
      
      We do need to check for spam when an issue changes from confidential to
      public, even if nothing else changed.
      d00b4a2e
  3. 04 Oct, 2018 1 commit
  4. 24 Sep, 2018 1 commit
  5. 21 Aug, 2018 1 commit
    • Sean McGivern's avatar
      Move Issue#{referenced,closed_by}_merge_requests to service · c73da6c1
      Sean McGivern authored
      These methods don't really need to be on the Issue model. Issue#related_branches
      can also be moved to a service, but we can do that in a separate commit.
      
      This commit does not change any behaviour; it just moves code around, renames
      the service, and refactors the specs.
      c73da6c1
  6. 11 Jul, 2018 1 commit
  7. 14 May, 2018 1 commit
  8. 19 Apr, 2018 1 commit
  9. 16 Apr, 2018 1 commit
  10. 13 Apr, 2018 1 commit
  11. 16 Mar, 2018 1 commit
  12. 22 Feb, 2018 1 commit
  13. 08 Jan, 2018 1 commit
  14. 02 Jan, 2018 1 commit
  15. 22 Dec, 2017 1 commit
  16. 06 Dec, 2017 1 commit
    • Yorick Peterse's avatar
      Throttle the number of UPDATEs triggered by touch · 856447cc
      Yorick Peterse authored
      This throttles the number of UPDATE queries that can be triggered by
      calling "touch" on a Note, Issue, or MergeRequest. For Note objects we
      also take care of updating the associated "noteable" relation in a
      smarter way than Rails does by default.
      856447cc
  17. 13 Nov, 2017 1 commit
  18. 11 Nov, 2017 1 commit
  19. 09 Oct, 2017 2 commits
  20. 30 Aug, 2017 1 commit
  21. 23 Aug, 2017 1 commit
    • Yorick Peterse's avatar
      Cache the number of open issues and merge requests · 6ec53f5d
      Yorick Peterse authored
      Every project page displays a navigation menu that in turn displays the
      number of open issues and merge requests. This means that for every
      project page we run two COUNT(*) queries, each taking up roughly 30
      milliseconds on GitLab.com. By caching these numbers and refreshing them
      whenever necessary we can reduce loading times of all these pages by up
      to roughly 60 milliseconds.
      
      The number of open issues does not include confidential issues. This is
      a trade-off to keep the code simple and to ensure refreshing the data
      only needs 2 COUNT(*) queries instead of 3. A downside is that if a
      project only has 5 confidential issues the counter will be set to 0.
      
      Because we now have 3 similar counting service classes the code
      previously used in Projects::ForksCountService has mostly been moved to
      Projects::CountService, which in turn is reused by the various service
      classes.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36622
      6ec53f5d
  22. 11 Aug, 2017 1 commit
  23. 09 Aug, 2017 1 commit
  24. 07 Aug, 2017 1 commit
  25. 02 Aug, 2017 1 commit
  26. 01 Aug, 2017 1 commit
  27. 27 Jul, 2017 1 commit
  28. 21 Jun, 2017 1 commit
  29. 14 Jun, 2017 1 commit
  30. 12 May, 2017 1 commit
  31. 04 May, 2017 2 commits
  32. 20 Apr, 2017 1 commit
  33. 11 Apr, 2017 1 commit
  34. 04 Apr, 2017 1 commit
  35. 21 Mar, 2017 1 commit
  36. 17 Mar, 2017 1 commit
  37. 14 Mar, 2017 2 commits