grimoirelab-perceval VS git-test

git-bug, the one mentioned in the article here, has some documentation on its README of how well its importer/exporter tools support Github, Gitlab, Jira, and Launchpad: https://github.com/MichaelMure/git-bug

Most of the other such tools I've seen barely have the resources to import/export a single such API. git-issue only has Github import it looks like. https://github.com/dspinellis/git-issue

There's perceval which is designed to be a generic archival tool and supports lots of APIs, but only dumps them to source-specific formats and would still need a lot of work if you tried to use issues from different APIs together: https://github.com/chaoss/grimoirelab-perceval

> I thought it was a neat article

I think the article talks about the "What" part of the problem, but the actual code is much more interesting in the "How" sense.

Like the git-ref stuff makes sense as you read the code

https://github.com/ligurio/git-test/blob/master/bin/git-test...

There was a similar set of additions to svn in the past with "svn propedit" in the workflows which I used in a previous workplace.

It was not pretty, because it was like embedding JIRA into svn - but it meant machines could flip state to state with commits during build+test and restart from that point without an independent DB to track the "current state" & people with commit access could nudge a stuck build out without losing "who did what".