Lassi Kortela <xxxxxx@lassi.io> writes:

>> I've thought about this, but I don't want to do this, and not only
>> because it's work.  It also ties us more closely to Github, which
>> I've always strived not to do, partly because free-software folks
>> have reasonable objections to Github, but also because I've learned
>> the hard way that tying oneself to someone else's platform is a
>> long-term risk.
>
> That's definitely true, but in case of hosting change (to GitLab or
> elsewhere) one would simply rig up a new batch job to export from that
> service instead. The issues and PRs are not an official channel, so
> people scavenging things from them could reasonably expect to
> encounter some inconvenience :)

Here's a tool that can store a bug tracker directly in the git
repository:

  https://github.com/MichaelMure/git-bug

It also comes with importers and exporters for GitHub, GitLab, Jira and
Launchpad. I don't have any personal experience with it though.

Regards,

--
Göran Weinholt   | https://weinholt.se/
Debian Developer | 73 de SA6CJK