BigW Consortium Gitlab

  1. 27 Oct, 2017 1 commit
    • Fix broken Members link when relative URL root paths are used · d6cd7006
      Stan Hu authored
      Navigating to the "Members" section of a project would omit the
      relative URL root path. Fix the redirection and eliminate the
      need for a redirection in the first place.
      
      Fix other redirections failing to work with relative roots
  2. 21 Oct, 2017 1 commit
  3. 18 Oct, 2017 1 commit
  4. 09 Oct, 2017 1 commit
  5. 06 Oct, 2017 2 commits
  6. 04 Oct, 2017 1 commit
  7. 03 Oct, 2017 1 commit
  8. 02 Oct, 2017 1 commit
  9. 28 Sep, 2017 2 commits
  10. 27 Sep, 2017 1 commit
    • Fixed breadcrumb title not linking · 05844d8b
      Phil Hughes authored
      This fixes the breadcrumb titles not having links. This was a regression
      in the updated breadcrumbs introduced in 10.0.
      
      This introduces the link for all pages rather than selectively doing it.
      This will cover issues, merge requests, pipelines, jobs etc.
      
      Closes #38059
  11. 22 Sep, 2017 1 commit
  12. 19 Sep, 2017 1 commit
  13. 18 Sep, 2017 1 commit
  14. 13 Sep, 2017 2 commits
  15. 08 Sep, 2017 1 commit
  16. 07 Sep, 2017 2 commits
  17. 06 Sep, 2017 5 commits
  18. 05 Sep, 2017 5 commits
  19. 04 Sep, 2017 2 commits
  20. 01 Sep, 2017 1 commit
  21. 31 Aug, 2017 2 commits
  22. 30 Aug, 2017 1 commit
  23. 25 Aug, 2017 1 commit
  24. 23 Aug, 2017 2 commits
    • 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
  25. 18 Aug, 2017 1 commit