A pull-mirror repository is not marked as such until after migration completes

[petergardfjall]

Description

Right now, a pull-mirror repo does not get properly marked as such until after the initial mirroring completes. That is, while it is being (mirror-)cloned, which can take quite some time depending on the size of the upstream repo, it will show up both in the API and in the UI as a regular repo.

• The first screenshot below shows the repo just after starting a pull-mirror migration. The repo is not marked as a mirror.

• The second screenshot below shows the repo a few minutes later when the mirror-cloning is complete. The repo is now marked as a mirror.

Gitea Version

main branch

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

tip of main branch

Operating System

Ubuntu 20.04

How are you running Gitea?

Local binary.

Database

PostgreSQL

[petergardfjall]

Proposed fix in #19295

[petergardfjall]

Fix merged.