- 02 Nov, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 06 Oct, 2017 1 commit
-
-
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.
-
- 14 Aug, 2017 1 commit
-
-
Robert Speicher authored
An upcoming update to rubocop-gitlab-security added additional violations.
-
- 24 Jul, 2017 1 commit
-
-
Tim Zallmann authored
-
- 05 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 02 May, 2017 1 commit
-
-
Bob Van Landuyt authored
If the cached html_field for a markdown_field is `nil` while the mfarkdown_field is not, it needs to be refreshed.
-
- 25 Apr, 2017 1 commit
-
-
Nick Thomas authored
Swap a before_save call with a before_create/before_update pair to avoid a confict with elasticsearch-model
-
- 21 Apr, 2017 2 commits
-
-
Nick Thomas authored
-
Nick Thomas authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 25 Jan, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 18 Jan, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 07 Oct, 2016 1 commit
-
-
Nick Thomas authored
This commit adds a number of _html columns and, with the exception of Note, starts updating them whenever the content of their partner fields changes. Note has a collision with the note_html attr_accessor; that will be fixed later A background worker for clearing these cache columns is also introduced - use `rake cache:clear` to set it off. You can clear the database or Redis caches separately by running `rake cache:clear:db` or `rake cache:clear:redis`, respectively.
-