I'm new to git-bug, I was mostly interested in the gitea bridge. I don't know if I'm using it wrong, but here is what I get when I do git bug bridge pull mybridge, after having configured it.

panic: runtime error: index out of range [-1]

goroutine 35 [running]:
github.com/MichaelMure/git-bug/bridge/gitea/iterator.(*issueIterator).Value(...)
        github.com/MichaelMure/git-bug/bridge/gitea/iterator/issue.go:39
github.com/MichaelMure/git-bug/bridge/gitea/iterator.(*Iterator).NextIssue(0xc0000b8120)
        github.com/MichaelMure/git-bug/bridge/gitea/iterator/iterator.go:90 +0x205
github.com/MichaelMure/git-bug/bridge/gitea.(*giteaImporter).ImportAll.func1()
        github.com/MichaelMure/git-bug/bridge/gitea/import.go:70 +0x92
created by github.com/MichaelMure/git-bug/bridge/gitea.(*giteaImporter).ImportAll
        github.com/MichaelMure/git-bug/bridge/gitea/import.go:66 +0x20a

git bug bridge auth correctly lists the gitea entry:

% git bug bridge auth
someid gitea-pre… token sometoken base-url:https://gitea.example,login:foo

go version go1.19.2 linux/amd64 on Archlinux.

I have added a single issue locally. This tracker doesn't have any issues yet. From a quick look this may be the issue?

I'm quite excited for this feature. It looks like the "only" big piece remaining is the export feature?

Looking at the code, it looks like something like that would fix that crash?

diff --git a/bridge/gitea/iterator/iterator.go b/bridge/gitea/iterator/iterator.go
index e3c701fa..9feef72b 100644
--- a/bridge/gitea/iterator/iterator.go
+++ b/bridge/gitea/iterator/iterator.go
@@ -85,12 +85,16 @@ func (i *Iterator) NextIssue() bool {
                return false
        }
 
+       if !more {
+               return false
+       }
+
        // Also reset the other sub iterators as they would
        // no longer be valid
        i.comment.Reset(i.issue.Value().Index)
        i.label.Reset(i.issue.Value().Index)
 
-       return more
+       return true
 }

I am not able to test though.

I'm quite excited for this feature. It looks like the "only" big piece remaining is the export feature?

That's correct. Would you like to take over?

The patch fixes it, thanks!

Would you like to take over?

I'm sorry, go isn't really my cup of tea, but most of all I already have my share of projects, I don't really have much time to put in new projects anymore. I may be able to test some things occasionally.

Closing in favor of #1017