-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Mirrors should not migrate refs/pull
and then the relative commits will be gone.
#27961
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
Comments
Hi @lunny gitea/services/mirror/mirror_pull.go Lines 478 to 480 in 846f618
![]() Is there a known work-around ? |
Thanks ! I'll test it when it's released |
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Nov 28, 2024
lunny
added a commit
that referenced
this issue
Nov 28, 2024
Backport #32659 by @lunny Fix #27961 Co-authored-by: Lunny Xiao <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
No response
Gitea Version
main
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?
Some filters should be applied in https://github.com/go-gitea/gitea/blob/main/services/mirror/mirror_pull.go#L225-L235 to not sync
refs/pull
for git mirror.Database
None
The text was updated successfully, but these errors were encountered: