From e364996c1d725a554f5f2bc01b03134ebe23ee4b Mon Sep 17 00:00:00 2001 From: Rui Barbosa Date: Wed, 18 Feb 2026 11:23:50 +0000 Subject: [PATCH] Clarify working with replicas --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bf1c280..21ada2e 100644 --- a/README.md +++ b/README.md @@ -32,10 +32,10 @@ There is a generic Git option with extra options for specific services. When mig Introduce the URL for the repository to migrate, and your login credentials/token. -If you want, you can set the new repository to be a replica (Gitea will automatically fetch changes from the original repository if it is updated, and push new changes). +If you want, you can set the new repository to be a replica (Gitea will automatically fetch changes from the original repository if it is updated). > [!Warning] -> Replicas can introduce merge conflics if work is being done on both sources at the same time. +> Replicas are pull only. No code can be pushed to replicas on Gitea. If you want to push code to Gitea, you have to convert the repository to a normal repository. External repositories can be configured as push targets, with Gitea automatically pushing your code to external services. Some options allow to migrate additional information, such as `Pull Requests`, `Issues` and `Tags`.