1. 07 Oct, 2017 3 commits
  2. 05 Oct, 2017 2 commits
  3. 02 Oct, 2017 3 commits
  4. 29 Sep, 2017 3 commits
  5. 28 Sep, 2017 1 commit
  6. 25 Sep, 2017 1 commit
  7. 20 Sep, 2017 2 commits
  8. 15 Sep, 2017 1 commit
  9. 14 Sep, 2017 1 commit
  10. 12 Sep, 2017 1 commit
  11. 07 Sep, 2017 1 commit
  12. 06 Sep, 2017 7 commits
  13. 05 Sep, 2017 1 commit
    • Rubén Dávila's avatar
      Optimize SQL queries used in Groups::GroupMembersController#create · 7b2ce0a538b8
      Rubén Dávila authored
      The following optimizations were performed:
      
      - Add new association to GroupMember and ProjectMember
      
        This new association will allow us to check if a user is a member of a
        Project or Group through a single query instead of two.
      
      - Optimize retrieving of Members when adding multiple Users
      7b2ce0a538b8
  14. 04 Sep, 2017 3 commits
  15. 31 Aug, 2017 4 commits
    • Zeger-Jan van de Weg's avatar
      079297bdaaba
    • Zeger-Jan van de Weg's avatar
      Implement the implied CI/CD config for AutoDevOps · 6427b5d35d8d
      Zeger-Jan van de Weg authored
      Behind an application setting, which defaults to false, this commit
      implements the implied CI/CD config. Which means that in the case we
      can't find the `.gitlab-ci.yml` on the commit we want to start a
      pipeline for, we fall back to an implied configuration.
      
      For now the Bash template has been copied to
      `Auto-Devops.gitlab-ci.yml` so the tests actually work.
      
      Fixes #34777
      6427b5d35d8d
    • Sean McGivern's avatar
      `current_application_settings` belongs on `Gitlab::CurrentSettings` · e1c28a485974
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
      e1c28a485974
    • Zeger-Jan van de Weg's avatar
      Don't show references to Pages when not available · 75dac8f30d3a
      Zeger-Jan van de Weg authored
      In this instance its subgroups, and given we can't deploy it, we
      shouldn't allow it to be shown.
      
      Fixes gitlab-org/gitlab-ce#34864
      75dac8f30d3a
  16. 30 Aug, 2017 1 commit
  17. 29 Aug, 2017 1 commit
  18. 28 Aug, 2017 1 commit
  19. 25 Aug, 2017 2 commits
  20. 24 Aug, 2017 1 commit