3 ms·
Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step. If you don't want speci
by morsch 11y ago
Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step.
If you don't want special git semantics around it, you'd have to be clever about how you store it so you don't have conflicts within the metadata. I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable.
- masklinn 11y ago> Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step. There were a number of tentative distributed bug trackers a few years ago, they sucked and fizzled out. IIRC Fossil is an attempt at an entire distributed project management system, I don't know how it fares. > I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable. That only works for your own personal project where you're the only user and contributor. Bug reporting by editing a markdown file (or even something actually usable like an org-mode file or an sqlite or BDB file) isn't going to scale very high and is way more effort than most bug reporters (even technical ones) will be willing to put in. And even if your users were willing to subject themselves to that, they still need a way to send back those contributions somehow.
- procrastitron 11y agogit-appraise (https://github.com/google/git-appraise https://github.com/google/git-appraise) does this for reviews and there is a tool (https://github.com/google/git-pull-request-mirror https://github.com/google/git-pull-request-mirror) for importing pull requests into the git-appraise format.