After importing some issues, the following problems occurred: incorrect open/closed status and missing content synchronization.

[tcitr-chen]

After importing some issues, the following problems occurred: incorrect open/closed status and missing content synchronization.

Gitea version: 1.25.3
Gitea Mirror version: 3.9.2

The first example

The second example

These are just a few issues I found by searching in chronological order; there are many more issues like these.

[arunavo4]

@tcitr-chen are these only on a few or like do you see any patterns here?

[tcitr-chen]

I haven't found any patterns yet. I just randomly discovered another one.

[arunavo4]

@tcitr-chen give this image a try ghcr.io/raylabshq/gitea-mirror:pr-162

[tcitr-chen]

It seems to work, but GitHub pull doesn't seem to sync to gitea.

[arunavo4]

It seems to work, but GitHub pull doesn't seem to sync to gitea.

@tcitr-chen

1. Is "Mirror Pull Requests" enabled in their Gitea config settings?
2. Is this a starred repository? If so, is "Starred Code Only" enabled? (This skips all metadata for starred repos)
3. What do the logs show? There's a diagnostic line that will reveal exactly which condition is failing:
   [Metadata] Pull request mirroring check: mirrorPullRequests=..., alreadyMirrored=..., isStarred=..., starredCodeOnly=..., shouldMirrorPullRequests=...

[tcitr-chen]

It seems that the status of issue is normal after import.
Some Pull Requests for projects on Github were imported into Gitea with incorrect open and closed states.
Here are some examples. @arunavo4

Gitea

Github url: dotnet/arcade-services#4903

second example.