GitLab steht wegen Wartungsarbeiten am Montag, den 10. Mai, zwischen 17:00 und 19:00 Uhr nicht zur Verfügung.

  1. 28 Jul, 2016 1 commit
  2. 27 Jul, 2016 1 commit
  3. 26 Jul, 2016 1 commit
  4. 23 Jul, 2016 1 commit
  5. 21 Jul, 2016 1 commit
  6. 20 Jul, 2016 8 commits
  7. 19 Jul, 2016 4 commits
  8. 18 Jul, 2016 3 commits
  9. 15 Jul, 2016 1 commit
  10. 13 Jul, 2016 5 commits
  11. 12 Jul, 2016 1 commit
  12. 07 Jul, 2016 2 commits
  13. 05 Jul, 2016 2 commits
    • Robert Speicher's avatar
      Dumb-down avatar presence check in `avatar_url` methods · c7b68b6e
      Robert Speicher authored
      `avatar.present?` goes through CarrierWave, and checks that the file
      exists on disk and checks its filesize. Because we're hitting the disk,
      this adds extra overhead to something where the worst-case scenario is
      rendering a broken image.
      
      Instead, we now just check that the _database attribute_ is present,
      which is good enough for our purposes.
      
      See https://gitlab.com/gitlab-org/gitlab-ce/issues/19273
      c7b68b6e
    • Timothy Andrew's avatar
      Support wildcard matches for protected branches at the model level. · f51af496
      Timothy Andrew authored
      1. The main implementation is in the `ProtectedBranch` model. The
         wildcard is converted to a Regex and compared. This has been tested
         thoroughly.
      
          - While `Project#protected_branch?` is the main entry point,
            `project#open_branches` and
            `project#developers_can_push_to_protected_branch?`
            have also been modified to work with wildcard protected branches.
      
          - The regex is memoized (within the `ProtectedBranch` instance)
      
      2. Improve the performance of `Project#protected_branch?`
      
          -  This method is called from `Project#open_branches` once _per branch_
             in the project, to check if that branch is protected or not.
      
          -  Before, `#protected_branch?` was making a database call every
             time it was invoked (in the above case, that amounts to once
             per branch), which is expensive.
      
          -  This commit caches the list of protected branches in memory, which
             reduces the number of database calls down to 1.
      
          -  A downside to this approach is that `#protected_branch?` _could_
             return a stale value (due to the caching), but this is
             an acceptable tradeoff.
      
      3. Remove the (now) unused `Project#protected_branch_names` method.
      
          - This was previously used to check for protected branch status.
      f51af496
  14. 01 Jul, 2016 1 commit
  15. 30 Jun, 2016 3 commits
  16. 29 Jun, 2016 1 commit
  17. 27 Jun, 2016 1 commit
  18. 22 Jun, 2016 1 commit
  19. 17 Jun, 2016 1 commit
  20. 16 Jun, 2016 1 commit
    • Yorick Peterse's avatar
      Fixed ordering in Project.find_with_namespace · 42598786
      Yorick Peterse authored
      This ensures that Project.find_with_namespace returns a row matching
      literally as the first value, instead of returning a random value.
      
      The ordering here is _only_ applied to Project.find_with_namespace and
      _not_ Project.where_paths_in as currently there's no code that requires
      Project.where_paths_in to return rows in a certain order. Since this
      method also returns all rows that match there's no real harm in not
      setting a specific order either. Another reason is that generating all
      the "WHEN" arms for multiple values in Project.where_paths_in becomes
      really messy.
      
      On MySQL we have to use the "BINARY" operator to turn a "WHERE" into a
      case-sensitive WHERE as otherwise MySQL may still end up returning rows
      in an unpredictable order.
      
      Fixes gitlab-org/gitlab-ce#18603
      42598786