1. 15 Nov, 2017 1 commit
  2. 09 Nov, 2017 1 commit
  3. 06 Nov, 2017 2 commits
  4. 04 Nov, 2017 1 commit
  5. 03 Nov, 2017 2 commits
  6. 02 Nov, 2017 1 commit
  7. 31 Oct, 2017 2 commits
  8. 30 Oct, 2017 1 commit
  9. 27 Oct, 2017 2 commits
    • Gabriel Mazetto's avatar
      Moved renaming operations to storage layer abstraction · 190b9c22851e
      Gabriel Mazetto authored
      When project storage_version is `2` means attachments are using
      hashed storage.
      190b9c22851e
    • Zeger-Jan van de Weg's avatar
      Cache commits on the repository model · 77de64bc4589
      Zeger-Jan van de Weg authored
      Now, when requesting a commit from the Repository model, the results are
      not cached. This means we're fetching the same commit by oid multiple times
      during the same request. To prevent us from doing this, we now cache
      results. Caching is done only based on object id (aka SHA).
      
      Given we cache on the Repository model, results are scoped to the
      associated project, eventhough the change of two repositories having the
      same oids for different commits is small.
      77de64bc4589
  10. 23 Oct, 2017 2 commits
  11. 17 Oct, 2017 1 commit
    • Bob Van Landuyt's avatar
      Fix errors when deleting a forked project · 192615692153
      Bob Van Landuyt authored
      The problem would occur when the `ForkedProjectLink` was deleted, but
      the `ForkNetworkMember` was not. The delete would be rolled back and
      retried.
      
      But the error would not be saved because `Project#forked?`
      would still be true, because the `ForkNetworkMember` exists. But the
      `Project#forked_project_link` would be `nil`. So the validation for
      the visibility level would fail.
      192615692153
  12. 13 Oct, 2017 1 commit
  13. 10 Oct, 2017 1 commit
  14. 07 Oct, 2017 3 commits
  15. 06 Oct, 2017 1 commit
    • Toon Claes's avatar
      Create idea of read-only database · a867cd2b92f4
      Toon Claes authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      
      Closes gitlab-org/gitlab-ce#37534.
      a867cd2b92f4
  16. 05 Oct, 2017 3 commits
  17. 04 Oct, 2017 4 commits
  18. 02 Oct, 2017 3 commits
  19. 29 Sep, 2017 3 commits
  20. 28 Sep, 2017 1 commit
  21. 25 Sep, 2017 1 commit
  22. 20 Sep, 2017 2 commits
  23. 15 Sep, 2017 1 commit