4 ms·
There's no standard, of course, but [shameless plug] I've recently built SIT (https://sit.fyi https://sit.fyi) -- a tool that allows to collaborate on informati
by yrashk 8y ago
There's no standard, of course, but [shameless plug] I've recently built SIT (https://sit.fyi https://sit.fyi) -- a tool that allows to collaborate on information in a decentralized, "true serverless" manner. Its first application is (duh!) issue tracking and it has been operational since almost day zero and SIT itself is using it. There's even a GitHub -> SIT import tool (pre-release)
Now, what's also great (did I mention "shameless"?) about the approach used in SIT is that while you can use it with Git (and this is how I've been using it so far), it does not depend on Git's structures but just files -- so it can be easily carried over to whatever might replace Git in a decade.
- btschaegg 8y agoGood to know, thank you very much for the link! I've just been thinking: If one manages issues within a separate git repo -- couldn't we also store pull requests this way? I've always been very impressed by how good `git diff` and `git apply` work together, so theoretically, one should just be able to store the result of `git diff master...HEAD` in a new issue. The rest sounds like a tooling problem...
- yrashk 8y agoSIT's issue tracking module stores merge requests (aka patches) in SIT itself, therefore, they can all be stored in a git repo. Case in point: https://github.com/sit-fyi/sit/commit/e9f96b84edc560bb1b0c0fa659908a9231ea165c https://github.com/sit-fyi/sit/commit/e9f96b84edc560bb1b0c0f... And this is how it looks in SIT: https://imgur.com/a/UCFmbsZ https://imgur.com/a/UCFmbsZ