3 ms·
I don't use GitHub Issues [much] because I was under the impression that issues are not themselves stored as a git repo, but rather they are some kind of propri
by dreamcompiler 5y ago
I don't use GitHub Issues [much] because I was under the impression that issues are not themselves stored as a git repo, but rather they are some kind of proprietary database GitHub maintains. Thus they create lockin for GitHub.
Am I wrong about this?
- Kaze404 5y agoYes. Issues are a Github feature, not a Git feature.
- mynameisvlad 5y agoI mean, isn't that the case for practically any issue tracking system? Which ones store their issue (and comments, etc) within the repo?
- Kaze404 5y agoFossil! https://www.fossil-scm.org/ https://www.fossil-scm.org/
- baby 5y agoWhy are you using Github if not for their social features?
- Lorin 5y agoGithub's social/discovery features are too strong - it makes it difficult to justify keeping OS projects on GitLab even if the feature set is better for maintainers
- dreamcompiler 5y agoI can't tell if you're joking, but if not I use it because it's a reliable, free git server.
- baby 5y agoNot sure why you’d think that. Maybe this is common in your circle but I don’t know anyone who uses github just to host a remote repo.
- CyberDildonics 5y agoYou literally have to pay to have a private repo. It isn't just a common use, it is feature you have to pay for.
- SilverRed 5y agoThe GDPR mandates that all web services allow you to export your data which github supports. Alternatives like gitlab allow you to import all of that "proprietary" data direct from github so its not a very strong lock in.