{"action":"created","issue":{"url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/94","repository_url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine","labels_url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/94/labels{/name}","comments_url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/94/comments","events_url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/94/events","html_url":"https://github.com/TeamPorcupine/ProjectPorcupine/issues/94","id":171749861,"number":94,"title":"Log Spam and Practices","user":{"login":"bjubes","id":7608114,"avatar_url":"https://avatars.githubusercontent.com/u/7608114?v=3","gravatar_id":"","url":"https://api.github.com/users/bjubes","html_url":"https://github.com/bjubes","followers_url":"https://api.github.com/users/bjubes/followers","following_url":"https://api.github.com/users/bjubes/following{/other_user}","gists_url":"https://api.github.com/users/bjubes/gists{/gist_id}","starred_url":"https://api.github.com/users/bjubes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bjubes/subscriptions","organizations_url":"https://api.github.com/users/bjubes/orgs","repos_url":"https://api.github.com/users/bjubes/repos","events_url":"https://api.github.com/users/bjubes/events{/privacy}","received_events_url":"https://api.github.com/users/bjubes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":22,"created_at":"2016-08-17T20:15:31Z","updated_at":"2016-08-18T20:14:39Z","closed_at":null,"body":"While it is very much encouraged to spam the log to your hearts content while testing, there should be some general guidelines on what debug messages should be allowed to be kept in a final PR. I am currently removing the more spammy ones to prevent lag and to find my own messages in the mix, but there should definitely be some written rules about this in either the CONTRIBUTING file or somewhere more fitting."},"comment":{"url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/comments/240842627","html_url":"https://github.com/TeamPorcupine/ProjectPorcupine/issues/94#issuecomment-240842627","issue_url":"https://api.github.com/repos/TeamPorcupine/ProjectPorcupine/issues/94","id":240842627,"user":{"login":"lameox","id":13168856,"avatar_url":"https://avatars.githubusercontent.com/u/13168856?v=3","gravatar_id":"","url":"https://api.github.com/users/lameox","html_url":"https://github.com/lameox","followers_url":"https://api.github.com/users/lameox/followers","following_url":"https://api.github.com/users/lameox/following{/other_user}","gists_url":"https://api.github.com/users/lameox/gists{/gist_id}","starred_url":"https://api.github.com/users/lameox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lameox/subscriptions","organizations_url":"https://api.github.com/users/lameox/orgs","repos_url":"https://api.github.com/users/lameox/repos","events_url":"https://api.github.com/users/lameox/events{/privacy}","received_events_url":"https://api.github.com/users/lameox/received_events","type":"User","site_admin":false},"created_at":"2016-08-18T20:14:38Z","updated_at":"2016-08-18T20:14:38Z","body":"Oh nice, i had not seen #185 go up. So far it looks like a good implementation/solution for our problem and definitely beats any solutions relying on compiler flags. for me in my initial suggestion that was more of a quick and dirty solution as i did not think we would implement a real wrapper this early.\r\n@bjubes i guess you can close this\r\n@Mizipzor would you say implementing a code analyzer like i suggested above would be a good idea for the future?\r\n"}}
{"actor":{"display_login":"lameox"}}