github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-07 21:17:16 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[GH-ISSUE #168] Mirror interval not match #1700

New Issue
Closed
opened 2026-04-27 19:00:57 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-27 19:00:57 -05:00
Owner
Copy Link

Originally created by @MMMMMoris on GitHub (Jan 20, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/168

Problem 1

I have made my gitea mirror settings as follow:

[mirror]
; Enables the mirror functionality. Set to **false** to disable all mirrors. Pre-existing mirrors remain valid but won't be updated; may be converted to regular repo.
ENABLED = true
; Disable the creation of **new** pull mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`.
DISABLE_NEW_PULL = false
; Disable the creation of **new** push mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`.
DISABLE_NEW_PUSH = false
; Default interval as a duration between each check
DEFAULT_INTERVAL = 48h
; Min interval as a duration must be > 1m
MIN_INTERVAL = 24h

I dont want to make a frequent sync, so I set MIN_INTERVAL = 24h. But after setting this, gitea-mirror cannot finish any job with a default interval as 8hr.

Image

It seems that settings here make no differences.

Image

Even though I changed the mirror interval from 8hr to 48hr manually in the mirrored gitea repository settings, it would be reset to 8hr by gitea-mirror after next scheduled sync, again.

I am really appreciated if this problem can resolved as soon as possible.

Problem 2

Is it possible to sync project description?
Every mirrored repository has no description, it's kind of wired to me.
Any support is thankful.

Problem 3

In the repository page, when you are operation, choose to sync or mirror or whatever, there will be a popping up message on the right bottom, which shadows the add repository button entirely.

They should not be place in the same location. At least do something to make add repository button available while message pops up. Now I have to wait until the message disappears to add another repository.

Obviously, pop up message can be placed on the left bottom, or just center top.

Image Image
Originally created by @MMMMMoris on GitHub (Jan 20, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/168 ## Problem 1 I have made my gitea mirror settings as follow: ```ini [mirror] ; Enables the mirror functionality. Set to **false** to disable all mirrors. Pre-existing mirrors remain valid but won't be updated; may be converted to regular repo. ENABLED = true ; Disable the creation of **new** pull mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`. DISABLE_NEW_PULL = false ; Disable the creation of **new** push mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`. DISABLE_NEW_PUSH = false ; Default interval as a duration between each check DEFAULT_INTERVAL = 48h ; Min interval as a duration must be > 1m MIN_INTERVAL = 24h ``` I dont want to make a frequent sync, so I set `MIN_INTERVAL = 24h`. But after setting this, gitea-mirror cannot finish any job with a default interval as 8hr. <img width="879" height="218" alt="Image" src="https://github.com/user-attachments/assets/be2151aa-acc6-4326-bf0c-5e5d8b5f5203" /> It seems that settings here make no differences. <img width="873" height="624" alt="Image" src="https://github.com/user-attachments/assets/12bcf9c1-6a93-4adf-a745-25be093d26d0" /> Even though I changed the mirror interval from 8hr to 48hr manually in the mirrored gitea repository settings, it would be reset to 8hr by gitea-mirror after next scheduled sync, again. I am really appreciated if this problem can resolved as soon as possible. ## Problem 2 Is it possible to sync project description? Every mirrored repository has no description, it's kind of wired to me. Any support is thankful. ## Problem 3 In the repository page, when you are operation, choose to sync or mirror or whatever, there will be a popping up message on the right bottom, which shadows the `add repository` button entirely. They should not be place in the same location. At least do something to make `add repository` button available while message pops up. Now I have to wait until the message disappears to add another repository. Obviously, pop up message can be placed on the left bottom, or just center top. <img width="1901" height="942" alt="Image" src="https://github.com/user-attachments/assets/024a8211-3bfe-4b1f-ad0c-a11cd577b722" /> <img width="1895" height="940" alt="Image" src="https://github.com/user-attachments/assets/a965260d-2079-4377-a325-1b716612f2ab" />
GiteaMirror commented 2026-04-27 19:01:06 -05:00
Author
Owner
Copy Link

@MMMMMoris commented on GitHub (Jan 20, 2026):

Problem 1 seems cannot be resolved by adding env GITEA_MIRROR_INTERVAL. I already have my gitea-mirror instance running.

<!-- gh-comment-id:3773015541 --> @MMMMMoris commented on GitHub (Jan 20, 2026): Problem 1 seems cannot be resolved by adding env `GITEA_MIRROR_INTERVAL`. I already have my gitea-mirror instance running.
GiteaMirror commented 2026-04-27 19:01:10 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Jan 21, 2026):

@MMMMMoris Thanks for the details for the problems. I will take a look this weeked and finish up a lot of pending issues

<!-- gh-comment-id:3777597033 --> @arunavo4 commented on GitHub (Jan 21, 2026): @MMMMMoris Thanks for the details for the problems. I will take a look this weeked and finish up a lot of pending issues
GiteaMirror commented 2026-04-27 19:01:13 -05:00
Author
Owner
Copy Link

@MMMMMoris commented on GitHub (Jan 21, 2026):

@MMMMMoris Thanks for the details for the problems. I will take a look this weeked and finish up a lot of pending issues

Hi there! Thanks for your attention. There’s another thoughtful feature: making repository issue syncing optional. This means I can decide which repositories will sync issues. Some repositories are updated via issues, similar to a BBS, where the issues matter more than the code. However, since most repositories primarily update code, making issue syncing customizable per repository is a great option.

<!-- gh-comment-id:3780660333 --> @MMMMMoris commented on GitHub (Jan 21, 2026): > [@MMMMMoris](https://github.com/MMMMMoris) Thanks for the details for the problems. I will take a look this weeked and finish up a lot of pending issues Hi there! Thanks for your attention. There’s another thoughtful feature: making repository issue syncing optional. This means I can decide which repositories will sync issues. Some repositories are updated via issues, similar to a BBS, where the issues matter more than the code. However, since most repositories primarily update code, making issue syncing customizable per repository is a great option.
GiteaMirror commented 2026-04-27 19:01:19 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Jan 22, 2026):

@MMMMMoris currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code?

<!-- gh-comment-id:3782041668 --> @arunavo4 commented on GitHub (Jan 22, 2026): @MMMMMoris currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code?
GiteaMirror commented 2026-04-27 19:01:21 -05:00
Author
Owner
Copy Link

@MMMMMoris commented on GitHub (Jan 22, 2026):

@MMMMMoris currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code?

Yes. Most repos choose code sync only as a default option, some other repos can choose to sync both code and issues.

<!-- gh-comment-id:3783620396 --> @MMMMMoris commented on GitHub (Jan 22, 2026): > [@MMMMMoris](https://github.com/MMMMMoris) currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code? Yes. Most repos choose code sync only as a default option, some other repos can choose to sync both code and issues.
GiteaMirror commented 2026-04-27 19:01:22 -05:00
Author
Owner
Copy Link

@MMMMMoris commented on GitHub (Jan 24, 2026):

@MMMMMoris currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code?

Image

One more mistake. The author of the original repo seems to be duplicated unnecessarily.

<!-- gh-comment-id:3794751383 --> @MMMMMoris commented on GitHub (Jan 24, 2026): > [@MMMMMoris](https://github.com/MMMMMoris) currently we have sync / dont sync for each repo but you want more control at each repo like for 1 repo dont sync issues, for another only sync code? <img width="1411" height="532" alt="Image" src="https://github.com/user-attachments/assets/ab543d56-e170-403c-9e80-ed19f867cf53" /> One more mistake. The author of the original repo seems to be duplicated unnecessarily.
GiteaMirror commented 2026-04-27 19:01:23 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Feb 24, 2026):

Thanks for the detailed report. I opened a fix PR here: https://github.com/RayLabsHQ/gitea-mirror/pull/182

What is included:

  • Repository descriptions are now mirrored to Gitea instead of being empty.
  • Toast notifications were moved to the top-right so they do not block the Add Repository floating button.
  • README now documents interval behavior with Gitea/Forgejo MIN_INTERVAL.

About interval behavior:

  • Gitea Mirror treats its configured mirror interval as the source of truth and applies it during sync.
  • If your server mirror.MIN_INTERVAL is higher than the app interval, mirror updates can fail.
  • Per-repo manual interval edits in Gitea/Forgejo are overwritten on the next sync from Gitea Mirror.

Recommended setup is to set Gitea Mirror interval greater than or equal to server MIN_INTERVAL.

<!-- gh-comment-id:3949044183 --> @arunavo4 commented on GitHub (Feb 24, 2026): Thanks for the detailed report. I opened a fix PR here: https://github.com/RayLabsHQ/gitea-mirror/pull/182 What is included: - Repository descriptions are now mirrored to Gitea instead of being empty. - Toast notifications were moved to the top-right so they do not block the Add Repository floating button. - README now documents interval behavior with Gitea/Forgejo MIN_INTERVAL. About interval behavior: - Gitea Mirror treats its configured mirror interval as the source of truth and applies it during sync. - If your server mirror.MIN_INTERVAL is higher than the app interval, mirror updates can fail. - Per-repo manual interval edits in Gitea/Forgejo are overwritten on the next sync from Gitea Mirror. Recommended setup is to set Gitea Mirror interval greater than or equal to server MIN_INTERVAL.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1700
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?