Skip to content
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

Feature request: Trigger push mirroring on change to source branch #16579

Closed
jotoho opened this issue Jul 30, 2021 · 3 comments
Closed

Feature request: Trigger push mirroring on change to source branch #16579

jotoho opened this issue Jul 30, 2021 · 3 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@jotoho
Copy link

jotoho commented Jul 30, 2021

  • Gitea version (or commit ref): 1.15.0+rc2 (docker image gitea/gitea:69d52290d01b)
  • Git version: 2.30.2
  • Operating system: Official docker image on 64-bit Raspberry Pi OS
  • Database: SQLite

Description

I would like to have the option for push mirroring to trigger on changes to the source branch instead of only happening on a fixed timer.

If a user, for example, prefers Gitea as a platform but mirrors their repository to another platform, like GitLab or GitHub, for running CI, then it wouldn't do them any good to have to wait potentially hours before getting their CI results from the secondary repository.

Changing the mirroring frequency to something like 10 minutes still wouldn't be ideal though and would place unnecessary load on Gitea and the mirror remote. (No need to synchronize changes every 10 minutes when the only user last touched the repo half a week ago)

I think that this use-case would best be addressed by adding the option for mirroring to trigger whenever the source branch on Gitea is changed instead of a timed trigger, maybe with a rate-limiting setting (i.e. pushing at most 5x an hour - if source branch is changed a sixth time in that hour, schedule a push for the start of the next hour) to slow down mirroring during particularly active periods.

@ansemjo ansemjo mentioned this issue Aug 7, 2021
6 tasks
@N-R-K
Copy link

N-R-K commented Sep 9, 2021

+1
Also I think it's sensible to wait 30~40sec to check if there's more changes before triggering a push.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Sep 9, 2021
@tgruenert
Copy link

We are in exactly same situation as @jotoho described before.
+1

@jotoho
Copy link
Author

jotoho commented Jul 14, 2022

Closing as it seems work has begun on issue #18220, which is a duplicate of this one.

@jotoho jotoho closed this as not planned Won't fix, can't repro, duplicate, stale Jul 14, 2022
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

4 participants