{"action":"created","issue":{"url":"https://api.github.com/repos/jeremygurr/dcssca/issues/205","repository_url":"https://api.github.com/repos/jeremygurr/dcssca","labels_url":"https://api.github.com/repos/jeremygurr/dcssca/issues/205/labels{/name}","comments_url":"https://api.github.com/repos/jeremygurr/dcssca/issues/205/comments","events_url":"https://api.github.com/repos/jeremygurr/dcssca/issues/205/events","html_url":"https://github.com/jeremygurr/dcssca/issues/205","id":148421507,"number":205,"title":"Issue management","user":{"login":"jeremygurr","id":3094011,"avatar_url":"https://avatars.githubusercontent.com/u/3094011?v=3","gravatar_id":"","url":"https://api.github.com/users/jeremygurr","html_url":"https://github.com/jeremygurr","followers_url":"https://api.github.com/users/jeremygurr/followers","following_url":"https://api.github.com/users/jeremygurr/following{/other_user}","gists_url":"https://api.github.com/users/jeremygurr/gists{/gist_id}","starred_url":"https://api.github.com/users/jeremygurr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeremygurr/subscriptions","organizations_url":"https://api.github.com/users/jeremygurr/orgs","repos_url":"https://api.github.com/users/jeremygurr/repos","events_url":"https://api.github.com/users/jeremygurr/events{/privacy}","received_events_url":"https://api.github.com/users/jeremygurr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-14T16:50:45Z","updated_at":"2016-04-14T20:33:38Z","closed_at":null,"body":"Feel free to create issues like you've been, it is working well. Don't close an issue unless you created it and are satisfied that it has been resolved. I'm leaving the ones open that are open because I'm either waiting for more input or am going to make a change to fix/implement it and it serves as a reminder for me. \r\n\r\nIf you create an issue for a bug, and you notice that it has been fixed, then go ahead and close it. I will sometimes leave those open to be sure that other's have verified it is working. \r\n\r\nFYI: for bug fixes I will sweep them for easy ones, take care of those, and then deal with the oldest hard one. Little by little they will disappear...\r\n\r\nFor example, if you have an idea, and it is discussed but not rejected, leave it open, because I probably intend to implement it. But if it is closed, I will forget about it and it probably won't happen.\r\n\r\nSometimes I will close an issue discussing an idea because it seems like the discussion is complete and I decided against implementing it. But if I don't close it, I'm either still considering it, or I want to implement it eventually, and I need it on the issue list until I do. \r\n\r\nSometimes I will reject an idea that I *would* like to implement, but it is too hard. Of course I would accept pull requests for these if someone else wanted to do the work. \r\n\r\nFor many ideas I don't want to implement, I would still accept a pull request for if someone else implemented it. If I didn't think it fit with my objectives here, I would likely *still* accept a pull request if it was optionized and it defaulted to off. \r\n"},"comment":{"url":"https://api.github.com/repos/jeremygurr/dcssca/issues/comments/210136327","html_url":"https://github.com/jeremygurr/dcssca/issues/205#issuecomment-210136327","issue_url":"https://api.github.com/repos/jeremygurr/dcssca/issues/205","id":210136327,"user":{"login":"yrmvgh","id":16616851,"avatar_url":"https://avatars.githubusercontent.com/u/16616851?v=3","gravatar_id":"","url":"https://api.github.com/users/yrmvgh","html_url":"https://github.com/yrmvgh","followers_url":"https://api.github.com/users/yrmvgh/followers","following_url":"https://api.github.com/users/yrmvgh/following{/other_user}","gists_url":"https://api.github.com/users/yrmvgh/gists{/gist_id}","starred_url":"https://api.github.com/users/yrmvgh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yrmvgh/subscriptions","organizations_url":"https://api.github.com/users/yrmvgh/orgs","repos_url":"https://api.github.com/users/yrmvgh/repos","events_url":"https://api.github.com/users/yrmvgh/events{/privacy}","received_events_url":"https://api.github.com/users/yrmvgh/received_events","type":"User","site_admin":false},"created_at":"2016-04-14T20:33:38Z","updated_at":"2016-04-14T20:33:38Z","body":"\"Discussion\" or \"chat\" tag?\r\n\r\nAlso, how do I make a pull request that uses several files? For instance there's a category called \"good_weapons\" which is referenced by fighter and gladiator.\r\n\r\nIf I create a category called \"ascetic_weapons\", and then have Monk refer to that category, all of those changes would (if accepted) need to happen at the same time - done one at a time, they'll break. Ho"}}