remote: mirror repository is read-only #32

New Issue

GiteaMirror · 2025-10-31T15:28:15-05:00

GiteaMirror commented

2025-10-31 15:28:15 -05:00

Originally created by @outbackdingo on GitHub (Jul 28, 2025).

so i mirrored all my remotes, i checked out a repo, maade a branch made some changes and committed them, when i tried to push its saying

remote: mirror repository is read-only

Originally created by @outbackdingo on GitHub (Jul 28, 2025). so i mirrored all my remotes, i checked out a repo, maade a branch made some changes and committed them, when i tried to push its saying remote: mirror repository is read-only

GiteaMirror added the enhancement question labels 2025-10-31 15:28:15 -05:00

GiteaMirror commented

2025-10-31 15:28:16 -05:00

@arunavo4 commented on GitHub (Jul 28, 2025):

@outbackdingo
This is intentional because:

Mirror repositories in Gitea are designed to be one-way syncs from the source
They automatically pull updates from GitHub on a schedule
Making changes directly would cause conflicts when the next sync occurs

You should make updates to Github so that it syncs back to gitea. But if you make changes in gitea and then something chnages in github you will break the auto sync as now we will have conflicts.

If you want to make changes and push them back, you have a few options:

Fork the mirror in Gitea to create a regular repository you can push to
Push changes back to GitHub instead, and they'll sync to Gitea automatically
Convert the mirror to a regular repository (but you'll lose automatic syncing)

@arunavo4 commented on GitHub (Jul 28, 2025): @outbackdingo This is intentional because: 1. Mirror repositories in Gitea are designed to be one-way syncs from the source 2. They automatically pull updates from GitHub on a schedule 3. Making changes directly would cause conflicts when the next sync occurs You should make updates to Github so that it syncs back to gitea. But if you make changes in gitea and then something chnages in github you will break the auto sync as now we will have conflicts. If you want to make changes and push them back, you have a few options: 1. Fork the mirror in Gitea to create a regular repository you can push to 2. Push changes back to GitHub instead, and they'll sync to Gitea automatically 3. Convert the mirror to a regular repository (but you'll lose automatic syncing)

GiteaMirror commented

2025-10-31 15:28:17 -05:00

@outbackdingo commented on GitHub (Jul 28, 2025):

i see, previously we could make changes to repos with mirror-to-gitea, most of the repos we mirror are yes just backup mirror, however we would like to utilize gitea for the working commit side on some repos. which commits would then push back to github, it would be nice if we could mirror all then flag certain repos to not sync both ways, say changes to git sync to gthub.

@outbackdingo commented on GitHub (Jul 28, 2025): i see, previously we could make changes to repos with mirror-to-gitea, most of the repos we mirror are yes just backup mirror, however we would like to utilize gitea for the working commit side on some repos. which commits would then push back to github, it would be nice if we could mirror all then flag certain repos to not sync both ways, say changes to git sync to gthub.

GiteaMirror commented

2025-10-31 15:28:17 -05:00

@arunavo4 commented on GitHub (Jul 28, 2025):

@outbackdingo Will have to think about this and maybe we can come up with something on the UI.

@arunavo4 commented on GitHub (Jul 28, 2025): @outbackdingo Will have to think about this and maybe we can come up with something on the UI.

GiteaMirror referenced this issue

2025-10-31 15:31:01 -05:00

[PR #32] [MERGED] Feat/v3 drizzle migrations #87

Sign in to join this conversation.