- 26 2月, 2020 1 次提交
-
-
由 GitLab Bot 提交于
-
- 25 9月, 2019 1 次提交
-
-
由 GitLab Bot 提交于
-
- 29 8月, 2018 1 次提交
-
-
由 Jacopo 提交于
-
- 07 8月, 2018 1 次提交
-
-
由 gfyoung 提交于
Partially addresses #47424.
-
- 22 11月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 18 9月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 31 8月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
-
- 08 8月, 2017 1 次提交
-
-
由 Brian Neel 提交于
-
- 06 7月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
- 22 3月, 2017 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 22 2月, 2017 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 20 2月, 2017 1 次提交
-
-
由 Z.J. van de Weg 提交于
-
- 07 2月, 2017 1 次提交
-
-
由 Jarka Kadlecova 提交于
-
- 02 2月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
Apply the same spam checks to public snippets (either personal snippets that are public, or public snippets on public projects) as to issues on public projects.
-
- 23 8月, 2016 1 次提交
-
-
由 Patricio Cano 提交于
-
- 16 8月, 2016 5 次提交
-
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
- Refactored SpamCheckService into SpamService
-
由 Patricio Cano 提交于
- Added controller actions as reusable concerns - Added controller tests
-
由 Patricio Cano 提交于
- Removed unnecessary column from `SpamLog` - Moved creation of SpamLogs out of its own service and into SpamCheckService - Simplified code in SpamCheckService. - Moved move spam related code into Spammable concern
-
由 Patricio Cano 提交于
- Merged `AkismetSubmittable` into `Spammable` - Clean up `SpamCheckService` - Added tests for `Spammable` - Added submit (ham or spam) options to `AkismetHelper`
-
- 27 7月, 2016 1 次提交
-
-
由 Patricio Cano 提交于
Refactor spam validation to a concern that can be easily reused and improve legibility in `SpamCheckService`
-