Read about our upcoming Code of Conduct on this issue

  1. 03 Oct, 2019 1 commit
  2. 01 Oct, 2019 1 commit
  3. 25 Sep, 2019 1 commit
  4. 13 Sep, 2019 1 commit
  5. 15 Aug, 2019 1 commit
  6. 25 Jul, 2019 1 commit
  7. 15 Jul, 2019 1 commit
  8. 12 Jul, 2019 1 commit
    • Robert Speicher's avatar
      Add Namespace#feature_available no-op · 2c5d5e2f859d
      Robert Speicher authored
      This gets overridden in `EE::Namespace` and allows us to do things like
      always treat Epics as "disabled" in Core using the same checks we'd use
  9. 09 Jul, 2019 1 commit
    • Bob Van Landuyt's avatar
      Lesser Namespace#name validations · e546183cdc39
      Bob Van Landuyt authored
      Since we use `Namespace#path` to build routes and URLs we can lessen
      the restrictions on `Namespace#name` so it can accomodate a user's name.
  10. 02 Jul, 2019 2 commits
    • Mayra Cabrera's avatar
      Includes logic to persist namespace statistics · da6d1b4d3fcd
      Mayra Cabrera authored
      - Add two new ActiveRecord models:
        - RootNamespaceStoragestatistics will persist root namespace statistics
        - NamespaceAggregationSchedule will save information when a new update
      to the namespace statistics needs to be scheduled
      - Inject into UpdateProjectStatistics concern a new callback that will
      call an async job to insert a new row onto NamespaceAggregationSchedule
      - When a new row is inserted a new job is scheduled. This job will
      update call an specific service to update the statistics and after that
      it will delete thee aggregated scheduled row
      - The RefresherServices makes heavy use of arel to build composable
      queries to update Namespace::RootStorageStatistics attributes.
      - Add an extra worker to traverse pending rows on
      NAmespace::AggregationSchedule table and schedule a worker for each one
      of this rows.
      - Add an extra worker to traverse pending rows on
      NAmespace::AggregationSchedule table and schedule a worker for each one
      of this rows
    • Adam Hegyi's avatar
      Memoizing root_ancestor in Namespace · 24fca74e2401
      Adam Hegyi authored
      The root_ancestor method is heavily used in EE for the group_saml
      feature. Having this memoization implemented in CE would eliminate
      the need of overriding the root_ancestor method in EE.
  11. 25 Jun, 2019 1 commit
    • Mayra Cabrera's avatar
      Add two new ActiveRecord models · a6131b0b8b44
      Mayra Cabrera authored
      - Namespace::Storagestatistics will persist root namespace statistics
      - Namespace::AggregationSchedule will save information when a new update
      to the namespace statistics needs to be scheduled
      Both tables use 'namespace_id' as primary key
  12. 31 May, 2019 1 commit
  13. 29 May, 2019 1 commit
  14. 02 May, 2019 1 commit
  15. 30 Apr, 2019 1 commit
  16. 23 Apr, 2019 1 commit
  17. 19 Apr, 2019 1 commit
  18. 12 Mar, 2019 1 commit
  19. 06 Mar, 2019 1 commit
  20. 15 Jan, 2019 1 commit
  21. 21 Dec, 2018 1 commit
  22. 19 Dec, 2018 1 commit
  23. 06 Dec, 2018 1 commit
    • Stan Hu's avatar
      Remove unnecessary includes of ShellAdapter · a3000dbddf80
      Stan Hu authored
      Determined by running the script:
      included = `git grep --name-only ShellAdapter`.chomp.split("\n")
      used = `git grep --name-only gitlab_shell`.chomp.split("\n")
      included - used
  24. 04 Dec, 2018 2 commits
    • Thong Kuah's avatar
      Unify into :group_clusters feature flag · 8954128c2d2d
      Thong Kuah authored
      With this MR, group clusters is now functional, so default to enabled.
      Have a single setting on the root ancestor group to enabled or disable
      group clusters feature as a whole
    • Thong Kuah's avatar
      Various improvements to hierarchy sorting · 25aaac800b56
      Thong Kuah authored
      - Rename ordered_group_clusters_for_project ->
      - Improve name of order option. It makes much more sense to have `hierarchy_order: :asc`
      and `hierarchy_order: :desc`
      - Allow ancestor_clusters_for_clusterable for group
      - Re-use code already present in Project
  25. 21 Nov, 2018 1 commit
  26. 05 Nov, 2018 1 commit
    • Olivier Gonzalez's avatar
      Backport generic methods to CE · 641bbafbcceb
      Olivier Gonzalez authored
      Allow to fetch all pipelines for every projects in a group and its
      Allow to fetch the latest pipeline id for each projects of a group and
      its subgroups.
  27. 01 Nov, 2018 1 commit
  28. 02 Oct, 2018 1 commit
  29. 24 Sep, 2018 1 commit
    • Michael Kozono's avatar
      Use `Gitlab::SafeRequestStore` in more places · 6f63147d8133
      Michael Kozono authored
      Even if it doesn’t save lines of code, since people will tend to use
      code they’ve seen. And `SafeRequestStore` is safer since you
      don’t have to remember to check ``.
  30. 17 Sep, 2018 1 commit
    • Yorick Peterse's avatar
      Added FromUnion to easily select from a UNION · 84f6b869d148
      Yorick Peterse authored
      This commit adds the module `FromUnion`, which provides the class method
      `from_union`. This simplifies the process of selecting data from the
      result of a UNION, and reduces the likelihood of making mistakes. As a
      result, instead of this:
          union =[foo, bar])
          Foo.from("(#{union.to_sql}) #{Foo.table_name}")
      We can now write this instead:
          Foo.from_union([foo, bar])
      This commit also includes some changes to make this new setup work
      properly. For example, a bug in Rails 4
      ( would break the use of
      `from("sub-query-here").includes(:relation)` in certain cases. There was
      also a CI query which appeared to repeat a lot of conditions from an
      outer query on an inner query, which isn't necessary.
      Finally, we include a RuboCop cop to ensure developers use this new
      module, instead of using Gitlab::SQL::Union directly.
  31. 06 Sep, 2018 1 commit
  32. 15 Aug, 2018 1 commit
  33. 01 Aug, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Add repository languages for projects · fc85a3572af6
      Zeger-Jan van de Weg authored
      Our friends at GitHub show the programming languages for a long time,
      and inspired by that this commit means to create about the same
      Language detection is done through Linguist, as before, where the
      difference is that we cache the result in the database. Also, Gitaly can
      incrementaly scan a repository. This is done through a shell out, which
      creates overhead of about 3s each run. For now this won't be improved.
      Scans are triggered by pushed to the default branch, usually `master`.
      However, one exception to this rule the charts page. If we're requesting
      this expensive data anyway, we just cache it in the database.
      Edge cases where there is no repository, or its empty are caught in the
      Repository model. This makes use of Redis caching, which is probably
      already loaded.
      The added model is called RepositoryLanguage, which will make it harder
      if/when GitLab supports multiple repositories per project. However, for
      now I think this shouldn't be a concern. Also, Language could be
      confused with the i18n languages and felt like the current name was
      suiteable too.
      Design of the Project#Show page is done with help from @dimitrieh. This
      change is not visible to the end user unless detections are done.
  34. 26 Jul, 2018 1 commit
  35. 25 Jul, 2018 1 commit
    • Yorick Peterse's avatar
      Remove code for dynamically generating routes · d9212d447768
      Yorick Peterse authored
      This adds a database migration that creates routes for any projects and
      namespaces that don't already have one. We also remove the runtime code
      for dynamically creating routes, as this is no longer necessary.
  36. 26 Jun, 2018 1 commit
  37. 31 May, 2018 1 commit
  38. 04 May, 2018 1 commit