Automatically update forks

In my instance of Gitea I have some mirror’s but in most of the cases I want to be able to make a simple change (mostly in the docker file, and now with gitea actions create a .gitea folder and automatically buid/push a container) to a repo and after that keep it automatically up to date. I found out that I need to create a mirror of the original repo and then create a fork of it to be able to change those settings. But after that I need to make manually PR’s and merge them. Is there any way to automate that (and maybe notify on an conflict)? maybe with gitea actions ? or is there already some script? I can’t imagine , I’m the only one wanting this.

2 Likes

The “Sync Fork” mechanism from Github would be really helpful …


I have several ansible role repos in place, and I routinely fork them for specific projects that use them as a base. Make updates etc. to accommodate the specific project.

The upstream repo is where real work is done though. But it would be very nice to have a simple web-UI method to pull updates from upstream into the fork.

1 Like

Since there is already issue for this, I think we can close this one.

You can use Gitea Actions to do the fork sync. Use cron job.

I really miss/love the Git sync fork option. This is a more cleaner way to remove/reduce conflicts and keeps greater control of the data sync across the forks and main repository.

The automatic sync, as described in some of the conversatons around this may not be the best. It is a good option. But better to leave that with the human who can best decide whether to automatically sync or manually do the pull to the fork to update the code.

Both choices are equally important.

Is there any chance we could do this same “Update branch” in a Form with Gitea?

I could find some similar conversations here:

How to update the forked repo from original repo · Issue #3271 · go-gitea/gitea

Pull upstream/master into fork · Issue #2488 · go-gitea/gitea

Maybe Support "merge upstream branch" (Sync fork) by wxiaoguang · Pull Request #32741 · go-gitea/gitea · GitHub have resolved this?

Yes @lunny . Thank you!