Proposal: extending/enhancing gitlab issue (and probably pull request) migration #8956

New Issue

GiteaMirror · 2025-11-02T08:24:03-06:00

GiteaMirror commented

2025-11-02 08:24:03 -06:00

Originally created by @Mai-Lapyst on GitHub (May 14, 2022).

Feature Description

Gitea currently imports comments on gitlab issues by using their Discussion/Note API.
However there are two problems:

unfortunately not everything in the comment section of an issue is included in the Discussion/Note API. Gitlab also has "Syntethic Notes" that are not given out by the normal notes API. They must be queried extra from various Event API's. For the Community Edition this would be: RessourceStateEvents (reopen/closing issue), RessourceLabelEvents (labels added/removed) and RessourceMilestoneEvents (for milestone assignment/clearing).
the normal notes also contains system messages (i.e assignments, un-/locking, changes to title...) which are only distingusihable with an boolean flag. Since the notes only hold text gitea currently just makes normal text-comments out of them.

I've investigates the gitlab API, and gitlabs behaviour and I think it could be possible to resolve these two problems. The second part could be resolved through some simply sting matching since the system messages are always marked as system, and their text content is pre-defined and always in english.

I also would work on this and submit an PR containing the necessary changes.

Screenshots

Gitlab:

Gitea (currently):

Gitea (what could be made; this was created manually)

Originally created by @Mai-Lapyst on GitHub (May 14, 2022). ### Feature Description Gitea currently imports comments on gitlab issues by using their Discussion/Note API. However there are two problems: 1. unfortunately not everything in the comment section of an issue is included in the Discussion/Note API. Gitlab also has "Syntethic Notes" that are not given out by the normal notes API. They must be queried extra from various Event API's. For the Community Edition this would be: RessourceStateEvents (reopen/closing issue), RessourceLabelEvents (labels added/removed) and RessourceMilestoneEvents (for milestone assignment/clearing). 2. the normal notes also contains system messages (i.e assignments, un-/locking, changes to title...) which are only distingusihable with an boolean flag. Since the notes only hold text gitea currently just makes normal text-comments out of them. I've investigates the gitlab API, and gitlabs behaviour and I think it could be possible to resolve these two problems. The second part could be resolved through some simply sting matching since the system messages are always marked as system, and their text content is pre-defined and always in english. I also would work on this and submit an PR containing the necessary changes. ### Screenshots Gitlab: ![image](https://user-images.githubusercontent.com/67418776/168439091-dd8557b6-3faf-47c8-ae0c-82cad84177fa.png) Gitea (currently): ![image](https://user-images.githubusercontent.com/67418776/168439032-5f575a31-90b8-4cbc-aecb-9c11292cb84f.png) Gitea (what could be made; this was created manually) ![image](https://user-images.githubusercontent.com/67418776/168439260-d9a12f69-bfdb-4135-894e-bf386102fa00.png)

GiteaMirror added the type/enhancement label 2025-11-02 08:24:03 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8956