[go: up one dir, main page]

Add a known issue in "import_export.md"

What does this MR do and why?

Add a known issue in import_export.md.

During the import/export process, only the most recent merge request diffs will be retained.

After multiple verifications and source code review, I found that this is a reproducible problem. In the exported data, the type of the merge_request_diff field is a dictionary rather than an array. Therefore, when there are multiple merge_request_diff, only one of them will be taken.

image

References

Screenshots or screen recordings

Before After

How to set up and validate locally

  1. In a project A, create an MR, submit multiple commits, and trigger multiple pipelines.
  2. Export project A and import it as project B.
  3. When viewing this MR in project B, it can be seen that there is only one pipeline left on the Pipelines page, and there is only one version of code that can be compared on the Changes page.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Zhiyuan Lu

Merge request reports

Loading