GitHub / relevance/log_buddy issues and pull requests
#13 - what do I do with all the `d`'s when I am in production?
Issue -
State: closed - Opened by angelacode about 8 years ago
#12 - way to remove info from the logs?
Issue -
State: closed - Opened by angelacode about 10 years ago
#11 - sending from log_buddy to a remote sys log?
Issue -
State: closed - Opened by angelacode about 10 years ago
- 9 comments
#10 - Update readme
Pull Request -
State: closed - Opened by mariozig almost 12 years ago
- 1 comment
#9 - Added ability to wrap output in a banner to make it easier to find
Pull Request -
State: closed - Opened by julescopeland over 12 years ago
- 1 comment
#8 - Fix option key name, :default_logger to :logger
Pull Request -
State: closed - Opened by lukaszx0 over 13 years ago
#7 - Fixing, cleaning and new features
Pull Request -
State: closed - Opened by alistairholt over 13 years ago
- 3 comments
#6 - Fix Rakefile when Jeweler is not installed
Pull Request -
State: closed - Opened by Flameeyes over 13 years ago
#5 - Rails 3 compatibility
Issue -
State: closed - Opened by jdpace about 15 years ago
- 1 comment
#4 - LogBuddy clobbers rails script/generate when running Ruby 1.9
Issue -
State: closed - Opened by rubyredrick over 15 years ago
- 1 comment
#3 - Should init itself by default on require
Issue -
State: closed - Opened by ghost about 16 years ago
- 1 comment
Labels: feature
#2 - still possible to get nil errors due to timing issues
Issue -
State: closed - Opened by ghost about 16 years ago
- 2 comments
Labels: fix
#1 - Ruby 1.9 compatibility
Issue -
State: closed - Opened by ghost about 16 years ago
- 5 comments
Labels: fix