4 ms·
You don't want your issue tracker in your source control if your product includes multiple source repositories, and a single bug might span several, or need to
by gnud 6y ago
You don't want your issue tracker in your source control if your product includes multiple source repositories, and a single bug might span several, or need to move between them.
Also, if you have customers who file bugs, they don't care about your code structure. And maybe they shouldn't have read access to your code?
- ocdtrekkie 6y agoFair points.
- haram_masala 6y agoLast I checked, GitHub lets you create projects that span multiple repos. But it’s still a good point that you shouldn’t be mangling your source control system to be a customer-facing support portal.
- threeseed 6y agoYou can just create an "issues" or "feedback" repository. Then you get the benefits of first-class integration with your code and CI/CD pipeline.