Administrator/getting-started
11
0
Fork 0
Code Issues Wiki Activity

Clarify working with replicas

Browse Source
This commit is contained in:
Rui Barbosa
2026-02-18 11:23:50 +00:00
parent b8d27afcd8
commit e364996c1d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -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`.