Read about our upcoming Code of Conduct on this issue

  1. 12 Jul, 2019 1 commit
  2. 10 Jul, 2019 2 commits
  3. 09 Jul, 2019 1 commit
  4. 03 Jul, 2019 1 commit
  5. 28 Jun, 2019 1 commit
  6. 27 Jun, 2019 1 commit
    • Thong Kuah's avatar
      Remove group_clusters feature flag · 32bc6b32a61b
      Thong Kuah authored
      Now we have terminals for instance and group clusters we can remove the
      FF now. Deploying to group clusters has been working without complaints
  7. 26 Jun, 2019 1 commit
  8. 24 Jun, 2019 1 commit
    • Stan Hu's avatar
      Re-add ignore_column for import columns · be7ad9d5fcf4
      Stan Hu authored
      This `ignore_column` was present for a while but recently removed, but
      to ensure we don't get error 500s let's keep it for a while.
  9. 19 Jun, 2019 1 commit
  10. 16 Jun, 2019 1 commit
  11. 14 Jun, 2019 1 commit
    • Stan Hu's avatar
      Fix inability to set visibility_level on project via API · 0a12e5313a85
      Stan Hu authored
      Consider the scenario:
      1. The default visibility level is set to internal
      2. A user attempts to create a private project within a private group
      Previously this would always fail because default_value_for would
      overwrite the private visibility setting, no matter what
      visibility_level were specified. This was happening because
      default_value_for was confused by the default value of 0 specified by
      the database schema.
      default_value_for attempts to assign the default value in the block by
      checking whether the attribute has changed. The problem is that since
      the default value by the database was 0, and the user requested 0, this
      appeared as though no changes were made. As a result, default_value_for
      would always overwrite the user's preference.
      To fix this, we remove the use of default_value_for and only set the
      visibility level to the default application setting when no preference
      has been given at creation time.
  12. 12 Jun, 2019 1 commit
    • Fabio Pitino's avatar
      Expose ci_default_git_depth via project API · 4534a11f54fe
      Fabio Pitino authored
      Enable Get and Update of ci_default_git_depth for
      Project API.
      Renaming Project#default_git_depth to :ci_default_git_depth
      to give more context through the API usage.
      Add API documentation
  13. 06 Jun, 2019 1 commit
    • Krasimir Angelov's avatar
      Add project level git depth setting · 4bf5744f969a
      Krasimir Angelov authored
      Introduce default_git_depth in project's CI/CD settings and set it to
      50. Use it if there is no GIT_DEPTH variable specified. Apply this
      default only to newly created projects and keep it nil for old ones
      in order to not break pipelines that rely on non-shallow clones.
      default_git_depth can be updated from CI/CD Settings in the UI, must be
      either nil or integer between 0 and 1000 (incl).
      Inherit default_git_depth from the origin project when forking projects.
      MR pipelines are run on a MR ref (refs/merge-requests/:iid/merge) and it
      contains unique commit (i.e. merge commit) which doesn't exist in the
      other branch/tags refs. We need to add it cause otherwise it may break
      pipelines for old projects that have already enabled Pipelines for merge
      results and have git depth 0.
      Document new default_git_depth project CI/CD setting
  14. 29 May, 2019 1 commit
  15. 20 May, 2019 1 commit
  16. 14 May, 2019 1 commit
  17. 10 May, 2019 1 commit
  18. 07 May, 2019 1 commit
  19. 06 May, 2019 2 commits
    • Ezekiel Kigbo's avatar
      Added blank lines to meet style guide · 5c1437e23f6e
      Ezekiel Kigbo authored
      Un-nest title variable output
      Update spec test names
      Rename sort_value_most_stars -> sort_value_stars_desc
      Rename sorted_by_stars -> sorted_by_stars_desc
      Renname sort_value_most_stars_asc -> sort_value_stars_asc
      Invert feature check, assign feature condition to a variable
      Inline conditional nav bar rendering
      Invert conditional label
      Added follow up task
      Fix filters returning 0 projects show the wrong view
      Move click action out of test expectation
      Use proper variable name for project in before block
      Rename projects_sort_admin_options_hash
      Renamed projects_sort_admin_options_has to
      old_projects_sort_options_hash as its not only used
      on the admin screen
      Fix extra whitespace errors
      Stub project_list_filter_bar in the projects_helper specs
      Added follow up task for `show_projects?`
      Removed url test expectations
    • Ezekiel Kigbo's avatar
  20. 02 May, 2019 1 commit
  21. 30 Apr, 2019 1 commit
  22. 26 Apr, 2019 1 commit
  23. 23 Apr, 2019 1 commit
  24. 20 Apr, 2019 1 commit
  25. 12 Apr, 2019 1 commit
  26. 11 Apr, 2019 1 commit
    • Thong Kuah's avatar
      Align UrlValidator to validate_url gem implementation. · 77da24aaafd6
      Thong Kuah authored
      Renamed UrlValidator to AddressableUrlValidator to avoid 'url:' naming collision with ActiveModel::Validations::UrlValidator in 'validates' statement.
      Make use of the options attribute of the parent class ActiveModel::EachValidator.
      Add more options: allow_nil, allow_blank, message.
      Renamed 'protocols' option to 'schemes' to match the option naming from UrlValidator.
  27. 10 Apr, 2019 2 commits
  28. 09 Apr, 2019 1 commit
  29. 08 Apr, 2019 1 commit
  30. 05 Apr, 2019 2 commits
  31. 02 Apr, 2019 1 commit
  32. 28 Mar, 2019 1 commit
  33. 27 Mar, 2019 2 commits
  34. 26 Mar, 2019 1 commit
    • Bob Van Landuyt's avatar
      Allow multiple repositories per project · 754b3795ec6b
      Bob Van Landuyt authored
      This changes the repository type from a binary `wiki?` to a type. So
      we can have more than 2 repository types.
      Now everywhere we called `.wiki?` and expected a boolean, we check
      that type.
  35. 22 Mar, 2019 1 commit