Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.1 on 2022-01-26 at 16:00 UTC+1 (a few minutes of down time)

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