07 May, 2013
6 commits
-
Return 422 HTTP status code when invalid API key
-
use charAt as array notation is not available in IE8
-
`"foo"[0]` is not available in IE < 9. Use `charAt` instead.
06 May, 2013
7 commits
-
Extract all concern about this call to his own class and move test to this class
-
Some test on spec/model/app are too specific to spec/model/error_report move to this spec
-
When a notice is do with an invalid api_key the return is a 404 HTTP code and no explain about what really happen. Now if you try post a notice with a bad API_KEY, errbit return a 422 HTTP status code, like doing by airbrake. see #472
-
Add some test with notice send with empty backtrace Add some test directly in the ErrorReport model
-
Add a helpful error message when non-admin users get a permission denied
05 May, 2013
2 commits
-
Extract the task in a class doing the job Add test on this class Update rspec and rspec-rails gems
-
The task db:clear_resolved can delete a lot of data. I think it can be good to repairDatabase after to avoid a big database. see #458
04 May, 2013
2 commits
-
launch a repairDatabase task on clear_resolved
03 May, 2013
3 commits
-
Complete the coverall integrations
-
Add the coverall badge on README Fix coverall coverage to add it on top of spec_helper Add simplecov report generation with launch spec with COVERAGE=true env
01 May, 2013
2 commits
-
Update Heroku config in README
-
mongolab free plan is now called "sandbox"
28 Apr, 2013
3 commits
25 Apr, 2013
2 commits
-
Use https urls for gems fetched from git
10 Apr, 2013
2 commits
-
Add a line reminding Heroku deployers to edit seeds.rb before pushing and running rake db:seed
09 Apr, 2013
2 commits
-
Commenting on an error when there is only one user raises an exception
08 Apr, 2013
5 commits
-
Include Code Climate Score in README.md Badge
-
updates the image in the README.md to include the current code climate score.
-
Test coverage for comment observer [Fixes #452]
-
Ruby 2.0 gem update
26 Mar, 2013
2 commits
-
Update the Airbrake domain in the README
21 Mar, 2013
2 commits
-
Capistrano: deploy from fixed branch
-
Not the 'current' branch in the local clone fo the repo. I feel like deploying from the current branch in the local clone is a bit presumptous. I expect most people want to deploy from one branch while allowing for development of several feature branches. Right now you always have to remember to check out master before deploying or you may deploy your feature branch (which may not even be pushed).
