3 ms·
If anyone has a good idea for a format/protocol to store issues & pull requests in Git itself, I'm all ears. There is a reason why every single product uses a
by Rjevski 8y ago
If anyone has a good idea for a format/protocol to store issues & pull requests in Git itself, I'm all ears.
There is a reason why every single product uses a separate database for those.
- yrashk 8y agoI've worked on this in SIT project (https://sit.fyi https://sit.fyi). While the core is generalized, the very first module available for it is issue tracking and I've been using it for a few months now. It enabled some scenarios previously difficult/impossible to achieve -- for example, merge requests can contain updates to issues as well, allowing one to make non-trivial updates to issues once their patch is merged in (for example, open a dozen of new issues [todo list for improving the new feature], leave comments, etc.)
- jwilk 8y agoSeparate (orphan) branch, which contains one markdown file for each issue/PR. If you figure out how to encode comment metadata and other pesky stuff like PR reviews, this should be both human and machine-readable.