An error occurred fetching the project authors.
  1. 10 Aug, 2016 1 commit
    • Yorick Peterse's avatar
      Remove trigram indexes for "ci_runners" · 17dd3e89
      Yorick Peterse authored
      These indexes are only used when you search for runners in the admin
      interface. This operation is so rarely used that it does not make sense
      to slow down every update in order to update the GIN trigram indexes.
      
      Removing these indexes should speed up queries such as those used for
      updating the last contact time of CI runners. Locally the timings of
      this query were reduced from ~50 ms to ~25 ms:
      
          UPDATE ci_runners SET updated_at = now(), contacted_at = now();
      17dd3e89
  2. 04 Aug, 2016 1 commit
  3. 03 Aug, 2016 1 commit
  4. 29 Jul, 2016 4 commits
    • Z.J. van de Weg's avatar
      Incorporate feedback · 76e9b684
      Z.J. van de Weg authored
      76e9b684
    • Z.J. van de Weg's avatar
      Add an URL field to Environments · be9aa7f1
      Z.J. van de Weg authored
      This MR adds a string (thus max 255 chars) field to the enviroments
      table to expose it later in other features.
      be9aa7f1
    • Timothy Andrew's avatar
      Use `Gitlab::Access` to protected branch access levels. · 0a8aeb46
      Timothy Andrew authored
      1. It makes sense to reuse these constants since we had them duplicated
         in the previous enum implementation. This also simplifies our
         `check_access` implementation, because we can use
         `project.team.max_member_access` directly.
      
      2. Use `accepts_nested_attributes_for` to create push/merge access
         levels. This was a bit fiddly to set up, but this simplifies our code
         by quite a large amount. We can even get rid of
         `ProtectedBranches::BaseService`.
      
      3. Move API handling back into the API (previously in
         `ProtectedBranches::BaseService#translate_api_params`.
      
      4. The protected branch services now return a `ProtectedBranch` rather
         than `true/false`.
      
      5. Run `load_protected_branches` on-demand in the `create` action, to
         prevent it being called unneccessarily.
      
      6. "Masters" is pre-selected as the default option for "Allowed to Push"
         and "Allowed to Merge".
      
      7. These changes were based on a review from @rymai in !5081.
      0a8aeb46
    • Timothy Andrew's avatar
      Add a series of migrations changing the model-level design of protected branch access levels. · f1e46d1e
      Timothy Andrew authored
      1. Remove the `developers_can_push` and `developers_can_merge` boolean
         columns.
      
      2. Add two new tables, `protected_branches_push_access`, and
         `protected_branches_merge_access`. Each row of these 'access' tables is
         linked to a protected branch, and uses a `access_level` column to
         figure out settings for the protected branch.
      
      3. The `access_level` column is intended to be used with rails' `enum`,
         with `:masters` at index 0 and `:developers` at index 1.
      
      4. Doing it this way has a few advantages:
      
         - Cleaner path to planned EE features where a protected branch is
           accessible only by certain users or groups.
      
         - Rails' `enum` doesn't allow a declaration like this due to the
           duplicates. This approach doesn't have this problem.
      
             enum can_be_pushed_by: [:masters, :developers]
             enum can_be_merged_by: [:masters, :developers]
      f1e46d1e
  5. 26 Jul, 2016 1 commit
  6. 21 Jul, 2016 1 commit
  7. 20 Jul, 2016 2 commits
  8. 19 Jul, 2016 3 commits
  9. 18 Jul, 2016 4 commits
  10. 16 Jul, 2016 1 commit
  11. 15 Jul, 2016 2 commits
  12. 14 Jul, 2016 1 commit
  13. 13 Jul, 2016 3 commits
  14. 12 Jul, 2016 2 commits
  15. 07 Jul, 2016 1 commit
    • Dravere's avatar
      Added setting to set new users by default as external · a0a9494e
      Dravere authored
      As requested by the issue #14508 this adds an option in the application
      settings to set newly registered users by default as external. The
      default setting is set to false to stay backward compatible.
      a0a9494e
  16. 06 Jul, 2016 1 commit
  17. 05 Jul, 2016 4 commits
  18. 30 Jun, 2016 2 commits
  19. 28 Jun, 2016 1 commit
  20. 20 Jun, 2016 3 commits
  21. 16 Jun, 2016 1 commit