Open jwflory opened 8 months ago
@jwflory, thanks for opening this issue ticket. As discussed in our 1:1 call last week, this investigation will have a comparatively lesser priority as I will be focused on fixing #60 and #96 for the v0.1.3 stable release. For this to be not blocked on just me, I will reach out to the team to see if anyone is willing to work on this and I will suggest you to do the same.
@gridhead Where do you suggest I reach out? What is the best practice here?
Summary
Copy the Markdown text from Pagure Pull Requests and comments into a corresponding GitLab Issue
Background
Pagure uses the same numbered sequence for issues and pull requests, while GitLab keeps the issue and merge request orders separate. Some Pagure projects have meaningful conversations about policies and decision inside of Pagure Pull Requests. For those projects which use Pagure Pull Requests in this meaningful way, migrating the Markdown comments (not the git diffs) is useful.
Details
To avoid gaps in the order of issues in GitLab, the Pagure Pull Requests can also be exported from Pagure into GitLab. This would only be the Markdown comments and none of the nuance of the git diffs or changes proposed.
Since this may be confusing for some teams, this should be opt-in behavior.
Outcome
Teams which use Pagure Pull Requests in a meaningful way will be able to preserve valuable conversations into GitLab