An error occurred fetching the project authors.
  1. 06 Sep, 2018 2 commits
  2. 05 Sep, 2018 1 commit
  3. 24 Jul, 2018 1 commit
  4. 11 Jul, 2018 1 commit
  5. 06 Jul, 2018 1 commit
  6. 12 Jun, 2018 1 commit
  7. 07 May, 2018 3 commits
  8. 04 May, 2018 1 commit
  9. 03 May, 2018 2 commits
  10. 30 Apr, 2018 1 commit
  11. 25 Apr, 2018 1 commit
  12. 24 Apr, 2018 1 commit
  13. 23 Apr, 2018 2 commits
  14. 28 Feb, 2018 2 commits
  15. 07 Feb, 2018 2 commits
  16. 05 Feb, 2018 1 commit
  17. 01 Feb, 2018 1 commit
  18. 30 Jan, 2018 1 commit
  19. 14 Dec, 2017 1 commit
  20. 06 Oct, 2017 1 commit
    • Toon Claes's avatar
      Create idea of read-only database · d1366971
      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.
      d1366971
  21. 28 Sep, 2017 2 commits
  22. 25 Aug, 2017 1 commit
  23. 22 Aug, 2017 2 commits
  24. 10 Aug, 2017 1 commit
  25. 04 Aug, 2017 1 commit
  26. 02 Aug, 2017 2 commits
  27. 01 Aug, 2017 1 commit
  28. 27 Jul, 2017 1 commit
  29. 30 Jun, 2017 1 commit
  30. 21 Jun, 2017 1 commit