to be able fork own repo to different names #4037

New Issue

GiteaMirror · 2025-11-02T05:35:13-06:00

GiteaMirror commented

2025-11-02 05:35:13 -06:00

Originally created by @ikozhukhov on GitHub (Sep 30, 2019).

Gitea version (or commit ref):
Git version: 1.9.3
Operating system: DilOS
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

example: i have created a mirrors of external repos and configured sync time.
i want create another repo as fork of mirrored repo for local commits, but i can't.
another example where i hate github: i can see 'illumos' repo and can fork it to my account only to one repo. 'openzfs' repo based on 'illumos' repo, but i can't for separate repo to my account if i did fork of one. i want separate repos because better to PR and both are repos have different commits on 'master' in the same time.
i like 'bitbucket' approach where i can fork own repo or remote repo to new name and use it.
i'd like to see the same ability in the fantastic one binary gitea!
help me please in this usecase!

Screenshots

Originally created by @ikozhukhov on GitHub (Sep 30, 2019).   - Gitea version (or commit ref): - Git version: 1.9.3 - Operating system: DilOS - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description example: i have created a mirrors of external repos and configured sync time. i want create another repo as fork of mirrored repo for local commits, but i can't. another example where i hate github: i can see 'illumos' repo and can fork it to my account only to one repo. 'openzfs' repo based on 'illumos' repo, but i can't for separate repo to my account if i did fork of one. i want separate repos because better to PR and both are repos have different commits on 'master' in the same time. i like 'bitbucket' approach where i can fork own repo or remote repo to new name and use it. i'd like to see the same ability in the fantastic one binary gitea! help me please in this usecase! ## Screenshots

GiteaMirror added the issue/stale label 2025-11-02 05:35:13 -06:00

GiteaMirror closed this issue

2025-11-02 05:35:13 -06:00

GiteaMirror commented

2025-11-02 05:35:14 -06:00

@lunny commented on GitHub (Oct 1, 2019):

I don't think this should be supported.

@lunny commented on GitHub (Oct 1, 2019): I don't think this should be supported.

GiteaMirror commented

2025-11-02 05:35:14 -06:00

@6543 commented on GitHub (Oct 3, 2019):

@ikozhukhov
if you realy like to have a "forg" you can do it manualy:

Creat new repo of your "forg"
Push all branches & co to new one -> https://gist.github.com/niksumeiko/8972566

@6543 commented on GitHub (Oct 3, 2019): @ikozhukhov if you realy like to have a "forg" you can do it manualy: 1. Creat new repo of your "forg" 2. Push all branches & co to new one -> https://gist.github.com/niksumeiko/8972566

GiteaMirror commented

2025-11-02 05:35:14 -06:00

@6543 commented on GitHub (Oct 3, 2019):

Or use a Organisation:
A:

Creat a Org (if you have none)
Forg repo to Org

B:

Creat a Org (if you have none)
Move repo to Org
Forg repo to you

@6543 commented on GitHub (Oct 3, 2019): Or use a Organisation: **A:** 1. Creat a Org (if you have none) 2. Forg repo to Org **B:** 1. Creat a Org (if you have none) 2. Move repo to Org 3. Forg repo to you

GiteaMirror commented

2025-11-02 05:35:14 -06:00

@guillep2k commented on GitHub (Oct 3, 2019):

Or use a Organisation:
A:

1. Creat a Org (if you have none)

2. Forg repo to Org

B:

1. Creat a Org (if you have none)

2. Move repo to Org

3. Forg repo to you

You cannot create an organization if you're not the site admin, AFAIK.

@guillep2k commented on GitHub (Oct 3, 2019): > > > Or use a Organisation: > **A:** > > 1. Creat a Org (if you have none) > > 2. Forg repo to Org > > > **B:** > > 1. Creat a Org (if you have none) > > 2. Move repo to Org > > 3. Forg repo to you You cannot create an organization if you're not the site admin, AFAIK.

GiteaMirror commented

2025-11-02 05:35:14 -06:00

@6543 commented on GitHub (Oct 3, 2019):

found a better solution: just "migrate" !

you can migreate a repo on gitea wich the instance itself is hosting to a new one

@6543 commented on GitHub (Oct 3, 2019): found a better solution: just "migrate" ! you can migreate a repo on gitea wich the instance itself is hosting to a new one

GiteaMirror commented

2025-11-02 05:35:15 -06:00

@stale[bot] commented on GitHub (Dec 2, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 2, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:35:15 -06:00

@stale[bot] commented on GitHub (Dec 16, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Dec 16, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:29:34 -06:00

[PR #4037] [MERGED] add api section to config cheat sheet #17209

GiteaMirror referenced this issue

2025-11-02 12:32:39 -06:00

[PR #4306] [MERGED] Create api-usage doc page #17326

Sign in to join this conversation.