3 ms·
I have a rough time understanding why I'd pick this over the issue tracker integrated with my source control. I get that it can sync with GitHub or GitLab (Does
by ocdtrekkie 6y ago
I have a rough time understanding why I'd pick this over the issue tracker integrated with my source control. I get that it can sync with GitHub or GitLab (Does it sync the issue text/comments such that GitHub users can comment on the issues? Are the issues on both sides using the same numbering? In this case, is Linear just a GitHub issues client?) but I imagine I am losing out on any given feature that my source control adds for issue integration, at least until Linear also does it.
Basically, I feel like you need to sell me a lot more on why I should use Linear over GitHub Issues, and how the benefits outweigh the added complexity of going two places.
- gnud 6y agoYou 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.