-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Mirror Summary #14608
Comments
I searched for "Mirror" on https://docs.gitea.io, and I didn't see much describing how mirrors run; Someone visiting |
@kdumontnu I think it's not the same. #3480 means a reverse mirror, #7609 means a mirror repository could be not readonly. |
Yes, mirror docs is also needed. |
@lunny thx, but the syntax is very confusing then. You say "Reverse mirroring #7609" above, but "#3480 means reverse mirror". Do you mean then: "Enable pushing to Gitea repo configured as secondary mirror #7609"? We can use consistent diction for mirrors as "primary (push)" and "secondary (pull)" Also, I added a bounty to #3480 if you can add the following:
|
Thanks, I have updated the issue content. I haven't followed your advise because I think |
Option to "protect" mirrors (dont sync if it will drop commits or is a completly new history) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I would suggest in addition to the issue #3480 to add the ability to only push certain branch, tags, etc. |
see also #18220 |
I order to prevent deleted or force-pushed commits from appearing in the GitHub Activity(and again), it would be nice to have some threshold on commit age when scheduled push mirror is enabled. Like once per a day push the only commits (tags, etc.), which older than 8 hours, for example. |
Mirror issues along with the repo Mirror issues along with the repo #1876The text was updated successfully, but these errors were encountered: