Matthias Simon
Matthias Simon
> It seems there is still a bug on the exporter, somehow. I also noticed two issues: * all imported bugs are "open" (when doing a `git bug ls` or...
Thank you for the context, Michael. I'll dig right into it. :-) The GitLab issue API response seems to provide a `state: {open, closed}` field: https://docs.gitlab.com/ce/api/issues.html#single-issue. I could not find...
Maybe I am still missing a point. Are you talking about the issue history on gitlab side? Do git-bug bugs also have a history?
I understand the issues with the GitLab API. I might have an idea how to fix the missing history in gitlab importer: Since GitLab 13.2 there's a API for retrieving...
It looks like it. However, I am not sure, because I am still familiarizing with git-bug and GitLab API.
I am sorry, I totally forgot about this issue. Must have gotten lost during my preparations for parental leave. 😶🌫️ Next week I will give you an update.
This seems to be a very useful feature indeed! I'd love to see your PR 😊
I will review your PR in a few days, when I am back from child leave. Is that okay with you?
Added benchmarks in https://github.com/nokia/ntt/pull/646 @nitinNT: Would this maybe interest you?
Sounds good to me. What you could do is executing the benchmarks before and after your change to see how big the improvement is.