BigW Consortium Gitlab

  1. 13 Sep, 2016 1 commit
  2. 12 Sep, 2016 1 commit
  3. 31 Aug, 2016 1 commit
  4. 19 Aug, 2016 1 commit
  5. 03 Aug, 2016 4 commits
  6. 02 Aug, 2016 1 commit
  7. 27 Jul, 2016 2 commits
  8. 26 Jul, 2016 1 commit
  9. 06 Jul, 2016 1 commit
  10. 21 Jun, 2016 1 commit
    • Optimize Banzai::Filter::RelativeLinkFilter · ca696175
      Alejandro Rodríguez authored
          A lot of git operations were being repeated, for example, to build a url
          you would ask if the path was a Tree, which would call a recursive routine
          in Gitlab::Git::Tree#where, then ask if the path was a Blob, which would
          call a recursive routine at Gitlab::Git::Blob#find, making reference to
          the same git objects several times. Now we call Rugged::Tree#path, which
          allows us to determine the type of the path in one pass.
      
          Some other minor improvement added, like saving commonly used references
          instead of calculating them each time.
  11. 08 Jun, 2016 1 commit
    • Remove `projects` inclusion in `notes_with_associations` to skip some unnecessary queries · ad83c308
      Alejandro Rodríguez authored
      `notes_with_associations` are used for `participant` declarations, but `Participable`
      only really cares about the target entity project, and not the participants
      projects.
      
      `notes_with_associations` are also used in `Commit::has_been_reverted?` which
      employs the reference extractor of the commit, so no references to the notes
      projects are made there (`Mentionable::all_references` cares only about the
      `author` and other `attr_mentionable`). A paralel situation occurs on
      `Issue::referenced_merge_requests`.
  12. 03 Jun, 2016 2 commits
  13. 02 Jun, 2016 1 commit
  14. 01 Jun, 2016 1 commit
    • Refactor Participable · 580d2501
      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.
  15. 19 Apr, 2016 2 commits
  16. 18 Apr, 2016 1 commit
  17. 13 Apr, 2016 1 commit
  18. 11 Apr, 2016 2 commits
  19. 01 Apr, 2016 1 commit
  20. 22 Mar, 2016 1 commit
  21. 03 Mar, 2016 1 commit
  22. 22 Feb, 2016 1 commit
  23. 19 Feb, 2016 11 commits