Skip to content

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

Closed
lunny opened this issue Nov 8, 2023 · 2 comments · Fixed by #32659
Closed

Mirrors should not migrate refs/pull and then the relative commits will be gone. #27961

lunny opened this issue Nov 8, 2023 · 2 comments · Fixed by #32659
Assignees
Labels

Comments

@lunny
Copy link
Member

lunny commented Nov 8, 2023

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

@lunny lunny added the type/bug label Nov 8, 2023
@ericLemanissier
Copy link
Contributor

Hi @lunny
It looks like this still happens, in spite of

if result.refName.IsPull() {
continue
}

image
Is there a known work-around ?

@ericLemanissier
Copy link
Contributor

Thanks ! I'll test it when it's released

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants