{"action":"opened","issue":{"url":"https://api.github.com/repos/sevatech/tech4health/issues/1","repository_url":"https://api.github.com/repos/sevatech/tech4health","labels_url":"https://api.github.com/repos/sevatech/tech4health/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/sevatech/tech4health/issues/1/comments","events_url":"https://api.github.com/repos/sevatech/tech4health/issues/1/events","html_url":"https://github.com/sevatech/tech4health/issues/1","id":178500436,"number":1,"title":"Repo versus Organization","user":{"login":"JtLively","id":18901899,"avatar_url":"https://avatars.githubusercontent.com/u/18901899?v=3","gravatar_id":"","url":"https://api.github.com/users/JtLively","html_url":"https://github.com/JtLively","followers_url":"https://api.github.com/users/JtLively/followers","following_url":"https://api.github.com/users/JtLively/following{/other_user}","gists_url":"https://api.github.com/users/JtLively/gists{/gist_id}","starred_url":"https://api.github.com/users/JtLively/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JtLively/subscriptions","organizations_url":"https://api.github.com/users/JtLively/orgs","repos_url":"https://api.github.com/users/JtLively/repos","events_url":"https://api.github.com/users/JtLively/events{/privacy}","received_events_url":"https://api.github.com/users/JtLively/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-22T01:31:01Z","updated_at":"2016-09-22T01:31:01Z","closed_at":null,"body":"For future growth, a Github organization may be a better idea and easier to follow. A repo is usually meant for a single project, not multiple. Things could get messy. "}}
{"actor":{"display_login":"JtLively"}}