1. 13 Feb, 2019 1 commit
  2. 06 Feb, 2019 1 commit
  3. 25 Jan, 2019 1 commit
    • Dennis Tang's avatar
      Refresh group overview to match project overview · 056f6dd0
      Dennis Tang authored
      - Avatar, group name, and group description now left-aligned
      - Notification setting and "New project" CTA right-aligned
        with group avatar and name
      - Leave group / request access now a link next to the 'Group'
        label below the group name
      - Notification setting label removed in favor of icons
        - Tooltip added to indicate notification setting
      - Search option moved inside table header next to "Sort by"
      056f6dd0
  4. 24 Jan, 2019 1 commit
  5. 14 Jan, 2019 1 commit
  6. 24 Dec, 2018 3 commits
  7. 04 Dec, 2018 1 commit
    • Thong Kuah's avatar
      Make subgroup specs :nested_groups · 885ea5c3
      Thong Kuah authored
      Subgroups are not supported in mySQL. I changed Namespace#root_ancestor
      to return from self_and_ancestors as a bugfix.
      
      ```
        184   # Returns all the ancestors of the current namespaces
        185   def ancestors
        186     return self.class.none unless parent_id
        187
        188     Gitlab::GroupHierarchy
        189       .new(self.class.where(id: parent_id))
        190       .base_and_ancestors
        191   end
      ```
      
      So it seems like on mySQL we accidentally returned the parent group :
      
      ```
      ancestors = self.class.where(id: parent_id)
      ancestors.reorder(nil).find_by(parent_id: nil)
      ```
      
      Project#root_namespace is used only by shared_runners_limit_namespace
      and all the tests for shared_runner_minutes_on_root_namespace are only
      enabled on `:nested_groups`
      
      `when :shared_runner_minutes_on_root_namespace is enabled', :nested_groups`
      
      We very clearly state in https://docs.gitlab.com/ee/user/group/subgroups/ that `
      Nested groups are only supported when you use PostgreSQL`, so I think I
      will fix forward and add `:nested_groups` to the two failing feature
      specs.
      885ea5c3
  8. 23 Oct, 2018 1 commit
  9. 15 Oct, 2018 1 commit
  10. 08 Sep, 2018 1 commit
  11. 06 Sep, 2018 1 commit
  12. 07 Aug, 2018 1 commit
  13. 11 Jul, 2018 1 commit
  14. 06 Jul, 2018 1 commit
  15. 05 Jul, 2018 1 commit
  16. 26 Feb, 2018 1 commit
  17. 23 Feb, 2018 1 commit
  18. 22 Dec, 2017 1 commit
  19. 02 Nov, 2017 1 commit
  20. 23 Oct, 2017 1 commit
  21. 17 Oct, 2017 1 commit
  22. 11 Oct, 2017 1 commit
  23. 07 Oct, 2017 3 commits
  24. 05 Sep, 2017 2 commits
  25. 17 Aug, 2017 1 commit
  26. 08 Aug, 2017 1 commit
  27. 07 Aug, 2017 2 commits
  28. 02 Aug, 2017 1 commit
  29. 01 Aug, 2017 1 commit
  30. 28 Jul, 2017 1 commit
    • Z.J. van de Weg's avatar
      Allow projects to be started from a template · 1d3815f8
      Z.J. van de Weg authored
      Started implementation for the first iteration of
      gitlab-org/gitlab-ce#32420. This will allow users to select a template
      to start with, instead of an empty repository in the project just
      created.
      
      Internally this is basically a small extension of the ImportExport
      GitLab projects we already support. We just import a certain import
      tar archive. This commits includes the first one: Ruby on Rails. In the
      future more will be added.
      1d3815f8
  31. 27 Jul, 2017 1 commit
  32. 06 Jul, 2017 1 commit
  33. 05 Jul, 2017 1 commit
  34. 29 Jun, 2017 1 commit