Duplicating a gitea repo (+setup) ? #6127

New Issue

GiteaMirror · 2025-11-02T06:45:49-06:00

GiteaMirror commented

2025-11-02 06:45:49 -06:00

Originally created by @chrisbward on GitHub (Oct 11, 2020).

Hi, not a bug - but just wondering if it's possible to copy an existing gitea repo/setup?

I have a project that I want to clone (copy) on the fly, and may need to do this multiple times.

I've noticed there's the fork method in the API (https://try.gitea.io/api/swagger#/repository/createFork), but it appears I'll only be able to do this once per organisation?

Originally created by @chrisbward on GitHub (Oct 11, 2020). Hi, not a bug - but just wondering if it's possible to copy an existing gitea repo/setup? I have a project that I want to clone (copy) on the fly, and may need to do this multiple times. I've noticed there's the fork method in the API (https://try.gitea.io/api/swagger#/repository/createFork), but it appears I'll only be able to do this once per organisation?

GiteaMirror added the type/question label 2025-11-02 06:45:49 -06:00

GiteaMirror closed this issue

2025-11-02 06:45:49 -06:00

GiteaMirror commented

2025-11-02 06:45:50 -06:00

@zeripath commented on GitHub (Oct 11, 2020):

You can fork and then make it not a fork?

@zeripath commented on GitHub (Oct 11, 2020): You can fork and then make it not a fork? ![Screenshot from 2020-10-11 21-11-47](https://user-images.githubusercontent.com/1824502/95689074-647a3600-0c06-11eb-89fb-05f2766fb6c5.png)

GiteaMirror commented

2025-11-02 06:45:50 -06:00

@chrisbward commented on GitHub (Oct 12, 2020):

Thanks - is this a newer feature? I can't seem to find it on 1.8.3.

I was able to fork the repo using the API, but only once...

@chrisbward commented on GitHub (Oct 12, 2020): Thanks - is this a newer feature? I can't seem to find it on 1.8.3. I was able to fork the repo using the API, but only once...

GiteaMirror commented

2025-11-02 06:45:50 -06:00

@6543 commented on GitHub (Oct 12, 2020):

@chrisbward could be, i highly recomend you to upgrade anyway ...

@6543 commented on GitHub (Oct 12, 2020): @chrisbward could be, i highly recomend you to upgrade anyway ...

GiteaMirror commented

2025-11-02 06:45:50 -06:00

@6543 commented on GitHub (Oct 12, 2020):

and if you like to create "closes" of a repo without having it liked as fork you can use the "migrate" feature/api

@6543 commented on GitHub (Oct 12, 2020): and if you like to create "closes" of a repo without having it liked as fork you can use the "migrate" feature/api

GiteaMirror commented

2025-11-02 06:45:50 -06:00

@lunny commented on GitHub (Oct 12, 2020):

Use template projects

@lunny commented on GitHub (Oct 12, 2020): Use template projects

GiteaMirror commented

2025-11-02 06:45:51 -06:00

@zeripath commented on GitHub (Oct 12, 2020):

Thanks - is this a newer feature? I can't seem to find it on 1.8.3.

Please upgrade.

There are 1880 lines of CHANGELOG.md between 1.8.3 and 1.12.5. 39 of those lines refer to Security issues. Over 8000 files have been changed with over a million lines with code insertion and nearly half a million lines, at least partly, deleted.

We can't support such old Giteas.

@zeripath commented on GitHub (Oct 12, 2020): > Thanks - is this a newer feature? I can't seem to find it on 1.8.3. Please upgrade. There are 1880 lines of CHANGELOG.md between 1.8.3 and 1.12.5. 39 of those lines refer to Security issues. Over 8000 files have been changed with over a million lines with code insertion and nearly half a million lines, at least partly, deleted. We can't support such old Giteas.

GiteaMirror commented

2025-11-02 06:45:51 -06:00

@chrisbward commented on GitHub (Oct 12, 2020):

Hi thanks - I upgraded, can now see the feature - but it isn't available in the API?

@chrisbward commented on GitHub (Oct 12, 2020): Hi thanks - I upgraded, can now see the feature - but it isn't available in the API?

GiteaMirror commented

2025-11-02 06:45:51 -06:00

@chrisbward commented on GitHub (Oct 12, 2020):

and if you like to create "closes" of a repo without having it liked as fork you can use the "migrate" feature/api

thanks - I will give that a try - assuming it does gitea to gitea migrations?

@chrisbward commented on GitHub (Oct 12, 2020): > and if you like to create "closes" of a repo without having it liked as fork you can use the "migrate" feature/api thanks - I will give that a try - assuming it does gitea to gitea migrations?

GiteaMirror commented

2025-11-02 06:45:51 -06:00

@6543 commented on GitHub (Oct 12, 2020):

@chrisbward gitea2gitea migration current state: only git repo itselve ... full migration will come soon ;)

@6543 commented on GitHub (Oct 12, 2020): @chrisbward gitea2gitea migration current state: only git repo itselve ... full migration will come soon ;)

GiteaMirror commented

2025-11-02 06:45:52 -06:00

@6543 commented on GitHub (Oct 12, 2020):

Hi thanks - I upgraded, can now see the feature - but it isn't available in the API?

I dont think converting a fork into a normal repo can be done via api at the moment

@6543 commented on GitHub (Oct 12, 2020): > Hi thanks - I upgraded, can now see the feature - but it isn't available in the API? I dont think converting a fork into a normal repo can be done via api at the moment

GiteaMirror commented

2025-11-02 06:45:52 -06:00

@6543 commented on GitHub (Oct 12, 2020):

(close because question was answerd)

@6543 commented on GitHub (Oct 12, 2020): (close because question was answerd)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6127