- 31 8月, 2016 4 次提交
-
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
adds test to check whether or not an email is sent to label subscribers after creating a new issue through the api
-
由 tiagonbotelho 提交于
-
- 16 8月, 2016 3 次提交
-
-
由 Patricio Cano 提交于
- Refactored SpamCheckService into SpamService
-
由 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 4 次提交
-
-
由 Patricio Cano 提交于
Refactor spam validation to a concern that can be easily reused and improve legibility in `SpamCheckService`
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
- 12 7月, 2016 1 次提交
-
-
由 Robert Schilling 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 Marc Siegfriedt 提交于
rely only on IssuesFinder docs and changelog
-
- 18 6月, 2016 2 次提交
-
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
This only supports Issues and MergeRequests right now because of the consistency of the routes those models provide.
-
- 08 6月, 2016 1 次提交
-
-
由 Alejandro Rodríguez 提交于
This was not a clear cut n+1 query, given that if you're directly subscribed to all issues that the API is returning you never really need to check for the notes. However, if you're subscribed to _all_ of them, then for each issuable you need to go once to `notes`, and once to `users` (for the authors). By preemtively loading notes and authors, at worst you have 1 extra query, and at best you saved 2n extra queries. We also took advantage of this preloading of notes when counting user notes.
-
- 03 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
This reverts commit 3e991230.
-
由 James Lopez 提交于
# Conflicts: # app/models/project.rb
-
- 13 5月, 2016 1 次提交
-
-
由 Ahmad Sherif 提交于
Closes #15638
-
- 28 4月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Previously all remote IPs appeared at 127.0.0.1, which made Akismet not very useful. Using the ActionDispatch Remote IP (http://api.rubyonrails.org/classes/ActionDispatch/RemoteIp.html) should provide more reliable results. Closes #16629
-
- 14 4月, 2016 1 次提交
-
-
由 Michael Greene 提交于
-
- 13 4月, 2016 6 次提交
-
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
- 08 4月, 2016 1 次提交
-
-
由 Robert Schilling 提交于
-
- 28 3月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 21 3月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 20 3月, 2016 3 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Zeger-Jan van de Weg 提交于
-
由 Zeger-Jan van de Weg 提交于
-
- 18 3月, 2016 1 次提交
-
-
- 02 2月, 2016 2 次提交
-
-
-
由 Stan Hu 提交于
Currently any spam detected by Akismet by non-members via API will be logged in a separate table in the admin page. Closes #5612
-
- 26 6月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
write_ was renamed to create_ modify_ was renamed to update_ So now in update action we have next code def create can?(current_user, :create_issue, @issue) end def update can?(current_user, :update_issue, @issue) end Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 02 5月, 2015 1 次提交
-
-
由 jubianchi 提交于
-
- 06 2月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-