-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
When the remote repository force push to overwrite a tag, the mirrored repo will not update the tag updated time #32233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Milestone
Comments
I cannot reproduce this problem according to the steps in my local machine. |
Hello, I just retested it and it can indeed be reproduced on demo.gitea.com.
A more detailed step-by-step guide is below, does this help?
![]() |
OK. Did you mean the problem is the updated time is not right? |
Yes, in my use case the updated time of tag v1 in the mirrored repo is wrong. |
lunny
added a commit
to lunny/gitea
that referenced
this issue
Nov 2, 2024
lunny
added a commit
that referenced
this issue
Nov 5, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When using the mirroring feature to sync a repo from another server, if the remote server force push overwrites a tag, the local server will not update the updated time of these tags after completing the synchronization.
Finally, we will see the following situation on the webui: two tags with different update times have the same commit id:

You can check the test repository I created (I've converted it to a regular repo to remove the personal server url I use for mirroring operations): https://demo.gitea.com/404notfound/test/tags
This is common when synchronizing GitHub Actions repositories, where tags containing only the major version number are often constantly updated to always point to the latest version.
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
run gitea from docker
Database
SQLite
Steps to reproduce
The text was updated successfully, but these errors were encountered: