Read about our upcoming Code of Conduct on this issue

  1. 07 May, 2019 1 commit
  2. 12 Mar, 2019 1 commit
  3. 21 Feb, 2019 1 commit
  4. 18 Feb, 2019 1 commit
  5. 08 Feb, 2019 1 commit
  6. 01 Feb, 2019 1 commit
  7. 27 Nov, 2018 1 commit
  8. 05 Oct, 2018 1 commit
  9. 06 Sep, 2018 2 commits
  10. 05 Sep, 2018 1 commit
  11. 24 Jul, 2018 1 commit
  12. 11 Jul, 2018 1 commit
  13. 06 Jul, 2018 1 commit
  14. 12 Jun, 2018 1 commit
  15. 07 May, 2018 3 commits
  16. 04 May, 2018 1 commit
  17. 03 May, 2018 2 commits
  18. 30 Apr, 2018 1 commit
  19. 25 Apr, 2018 1 commit
  20. 24 Apr, 2018 1 commit
  21. 23 Apr, 2018 2 commits
  22. 28 Feb, 2018 2 commits
  23. 07 Feb, 2018 2 commits
  24. 05 Feb, 2018 1 commit
  25. 01 Feb, 2018 1 commit
  26. 30 Jan, 2018 1 commit
  27. 14 Dec, 2017 1 commit
  28. 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
  29. 28 Sep, 2017 2 commits
  30. 25 Aug, 2017 1 commit
  31. 22 Aug, 2017 2 commits