1. 29 Jun, 2016 1 commit
  2. 27 Jun, 2016 1 commit
  3. 16 Jun, 2016 3 commits
    • Yorick Peterse's avatar
      Fixed ordering in Project.find_with_namespace · 5fa0a6c1a212
      Yorick Peterse authored
      This ensures that Project.find_with_namespace returns a row matching
      literally as the first value, instead of returning a random value.
      The ordering here is _only_ applied to Project.find_with_namespace and
      _not_ Project.where_paths_in as currently there's no code that requires
      Project.where_paths_in to return rows in a certain order. Since this
      method also returns all rows that match there's no real harm in not
      setting a specific order either. Another reason is that generating all
      the "WHEN" arms for multiple values in Project.where_paths_in becomes
      really messy.
      On MySQL we have to use the "BINARY" operator to turn a "WHERE" into a
      case-sensitive WHERE as otherwise MySQL may still end up returning rows
      in an unpredictable order.
      Fixes gitlab-org/gitlab-ce#18603
    • James Lopez's avatar
      Revert "squashed merge and fixed conflicts" · 91545d127ac6
      James Lopez authored
      This reverts commit 429cd5e57fb1.
    • James Lopez's avatar
      squashed merge and fixed conflicts · 429cd5e57fb1
      James Lopez authored
  4. 15 Jun, 2016 3 commits
  5. 14 Jun, 2016 6 commits
  6. 13 Jun, 2016 1 commit
  7. 10 Jun, 2016 3 commits
    • Kamil Trzcinski's avatar
      Added initial version of deployments · 44c63e4f59c9
      Kamil Trzcinski authored
    • Paco Guzman's avatar
      Cache the presence of an issue_tracker at project level · 224a9e3917df
      Paco Guzman authored
      Using update_column to store the boolean flag to avoid
      any side effects with the current state of the project
    • Yorick Peterse's avatar
      Add Project.where_paths_in · d80adaa274f4
      Yorick Peterse authored
      This method can be used to find multiple projects for multiple paths.
      For example, take this snippet:
          Project.where_paths_in(%w{gitlab-org/gitlab-ce gitlab-org/gitlab-ee})
      This will return an ActiveRecord::Relation containing the GitLab CE and
      GitLab EE projects.
      This method takes care of matching rows both case-sensitively and
      case-insensitively where needed.
      Project.find_with_namespace in turn has been modified to use
      Project.where_paths_in without nuking any scoping (instead it uses
      reorder(nil)). This means that any default scopes (e.g. those used for
      "pending_delete" stay intact).
      The method Project.where_paths_in was added so the various Markdown
      filters can use a single query to grab all the projects referenced in a
      set of documents, something Project.find_with_namespace didn't allow.
  8. 03 Jun, 2016 4 commits
  9. 02 Jun, 2016 4 commits
  10. 01 Jun, 2016 2 commits
  11. 30 May, 2016 1 commit
  12. 25 May, 2016 1 commit
  13. 24 May, 2016 1 commit
    • Phil Hughes's avatar
      Updated erorr message when project limit is zero · cee1020e226f
      Phil Hughes authored
      When the project limit is zero & the user tries to create a project, the error displayed is now 'Personal project creation is not allowed. Please contact your administrator with questions'
      Closes #17691
  14. 20 May, 2016 2 commits
  15. 19 May, 2016 1 commit
  16. 18 May, 2016 2 commits
  17. 17 May, 2016 1 commit
  18. 16 May, 2016 2 commits
  19. 14 May, 2016 1 commit