> Having to create issues-only repositories seems like a sign that one may be using the wrong tool. Use it to track white papers, project planning documents, a

> Having to create issues-only repositories seems like a sign that one may be using the wrong tool. Use it to track white papers, project planning documents, a project-wide wiki, et c., if you want to feel like it's for more than just issues. Though having an issues-only project doesn't seem worse to me than using any other stand-alone issue tracker, separate from GH.