hey @voronoipotato! i've recently joined as a maintainer and noticed that you closed this and dspinellis/git-issue#97 earlier this year.

is this still something you'd like to explore and converse about?

it's late for me, so apologies for the brevity of the remarks below, but i'll try to enumerate some initial findings from a quick glance, as it appears there are very stark differences:

• go vs. posix-y shell
• git-bug has bridges to third party platforms (e.g. sync w/ github issues)
• git-bug provides three UIs: cli, tui, web vs git-issue's cli
• no, i don't believe the data models are interopable at all; git-issues appears to be using commit hashes (of HEAD) as identifiers; entities in git-bug are disassociated from commit identifiers (although it used to use sha-1 hashes, likely back when you asked this question)
• git-issues appears to store files in a repository; git-bug stores objects, and doesn't create files on your filesystem

that's all i have time for right now. if you or other users are interested in a more thorough comparison, i'll create an issue for diving deep into git-issues to understand it better than i can with the limited time i had tonight.