Does the GitLab bridge support merge requests?

I've just configured the bridge and pulled all the issues. That part seems to work well.

When I run git bug ls I don't see any merge requests.

I don't see any option to list them separately.

When I search for the merge request using known content, git-bug doesn't show it: git bug ls "known content"

git-bug is an issue tracker, not a code review tool. can you clarify what you're expecting git-bug to do in relation to merge requests?

sudoforge added label triage/needs-information 11 months ago

My general use case: I want to archive all the project communication made via GitLab. I'm a user of the the GitLab project and not an administrator. I can't just make a full backup of the whole project. GitLab's own issues export for users is weak (CSV file!?).

I am hoping that git-bug gives me another way to export all the communication from issues and pull requests.

git-bug already apparently does this for GitLab issues, which is a great start. I can use it to browse the communication on GitLab issues even when I don't have access to GitLab.com. I want the same experience for pull requests.

I don't care about the code-review features of a pull request. The part that matters to me is the part that is like an issue: the stream of comments.

I think it would be great if git-bug could at least list which pull requests exist and archive their descriptions and lists of comments on them. I realize that might be complicated by the fact that pull requests have the concept of comments on revisions and lines, but I can live without that context if it's hard to capture. What matters most is who said what when.

I had some trouble getting started with git-bug earlier (#1327) so I ended up using another simpler tool to export all the GitLab issues from a project. (mklilley/gitlab-issue-backup).

That other tool doesn't address GitLab pull requests either. So right now there is a gap in my archiving.

My workaround for this gap is to keep all project-oriented communication in an issue and out of the pull request. If anything important does leak into a pull request, I'll have to copy and link it in a corresponding issue.

that's an interesting use case, for sure, but unfortunately it doesn't really fit in with the design and purpose of git-bug in its current (or any planned future) form, so i'm going to close this issue for now. as an alternative way to accomplish your goal, you might take a look at the following APIs from gitlab:

• list merge requests: https://docs.gitlab.com/api/merge_requests/#list-merge-requests
• list notes for a merge request: https://docs.gitlab.com/api/notes/#list-all-merge-request-notes

hitting these and transforming the response in whatever format you want for archival would accomplish your goal. of course, you don't have the UI provided with a tool like git-bug for browsing those, but i thought i'd provide this context to you in case it was useful.

sudoforge closed the bug 11 months ago

sudoforge removed label triage/needs-information 11 months ago

sudoforge added label triage/unresolved 11 months ago

sudoforge added label resolution/no-action-planned 11 months ago

Thanks @sudoforge, that all makes sense. I get why you don't want to put that into git-bug.

Thanks for the pointers to the API!