Read about our upcoming Code of Conduct on this issue

  1. 07 May, 2019 1 commit
  2. 20 Apr, 2019 1 commit
  3. 10 Apr, 2019 2 commits
  4. 09 Apr, 2019 1 commit
  5. 05 Apr, 2019 3 commits
  6. 02 Apr, 2019 1 commit
  7. 01 Apr, 2019 1 commit
  8. 27 Mar, 2019 1 commit
  9. 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.
      754b3795ec6b
  10. 22 Mar, 2019 1 commit
  11. 13 Mar, 2019 1 commit
  12. 12 Mar, 2019 1 commit
  13. 07 Mar, 2019 1 commit
  14. 01 Mar, 2019 2 commits
  15. 27 Feb, 2019 1 commit
    • Jacopo's avatar
      Add project http fetch statistics API · 89bd31e7300c
      Jacopo authored
      The API get projects/:id/traffic/fetches allows user with write
      access to the repository to get the number of clones for the
      last 30 days.
      89bd31e7300c
  16. 26 Feb, 2019 1 commit
  17. 25 Feb, 2019 1 commit
  18. 20 Feb, 2019 2 commits
  19. 11 Feb, 2019 1 commit
  20. 08 Feb, 2019 2 commits
  21. 06 Feb, 2019 1 commit
  22. 31 Jan, 2019 2 commits
  23. 29 Jan, 2019 1 commit
    • Andreas Brandl's avatar
      Flush InternalId records after import · 08cbb3d84cef
      Andreas Brandl authored
      After the import has finished, we flush (delete) the InternalId records
      related to the project at hand. This means we're starting over with
      tracking correct internal id values, a new record will be created
      automatically when the next internal id is generated.
      
      The GitHub importer assigns iid values by using supplied values from
      GitHub. We skip tracking internal id values during the import in favor
      of higher concurrency. Deleting any InternalId records after the import
      has finished is an extra measure to guarantee consistency.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54270.
      08cbb3d84cef
  24. 28 Jan, 2019 1 commit
  25. 25 Jan, 2019 1 commit
    • Gabriel Mazetto's avatar
      Refactor Storage Migration · ab819a7a1396
      Gabriel Mazetto authored
      Specs were reviewed and improved to better cover the current behavior.
      There was some standardization done as well to facilitate the
      implementation of the rollback functionality.
      
      StorageMigratorWorker was extracted to HashedStorage namespace were
      RollbackerWorker will live one as well.
      ab819a7a1396
  26. 24 Jan, 2019 1 commit
  27. 21 Jan, 2019 1 commit
  28. 16 Jan, 2019 1 commit
    • Yorick Peterse's avatar
      Refactor checking personal project limits · da8b222b69e8
      Yorick Peterse authored
      This refactors the code used for checking if a user has exceeded the
      personal projects limit. As part of this refactor the method has been
      renamed from Project#check_limit to "check_personal_projects_limit", as
      this name makes it much more clear what the purpose of the method is.
      Standalone unit tests have also been added, as before we only had a
      single generic validation test that did not cover all cases.
      
      The old implementation of the refactored method also included a `rescue`
      statement. This code would only run when a project creator was not set.
      The error that would be added wasn't super useful, especially since
      there would already be errors for the creator not being present. As none
      of the other code in the "check_personal_projects_limit" raises, it has
      been removed.
      da8b222b69e8
  29. 14 Jan, 2019 1 commit
  30. 11 Jan, 2019 2 commits
  31. 09 Jan, 2019 1 commit
    • Steve Azzopardi's avatar
      Remove get_build method for find_by_id · 2f9c04015f7b
      Steve Azzopardi authored
      The original intention of `get_build` was as a workaround not to violate
      `CodeReuse/ActiveRecord`. `find_by_id` does the exact same thing but
      does not violate the rubocop rule.
      2f9c04015f7b
  32. 07 Jan, 2019 1 commit
    • Gabriel Mazetto's avatar
      Only set as `read_only` when starting the per-project migration · 10d9a7b13e9f
      Gabriel Mazetto authored
      In the previous code, we locked the project during the migration
      scheduling step, which works fine for small setups, but can be
      problematic in really big installations.
      
      We now moved the logic to inside the worker, so we minimize the time a
      project will be read-only. We also make sure we only do that if
      reference counter is `0` (no current operation is in progress).
      10d9a7b13e9f