(james here)<p>There are a few tools that do this already. I think it&#x27;s an interesting approach, and probably makes sense for some people.<p>However, I feel like tying issues to closely to the code can be problematic. For example, for the product Ship itself there are multiple repositories, there&#x27;s the server, the client, the web site, and a few libraries that we built along the way and open sourced.<p>We want to be able to file issues on our product without having to first determine in which repo the problem actually resides. We also want to be able to file umbrella issues or features that require us to make cross cutting code changes across multiple repositories.