Extend fork API to support custom repo name and owner

[yosiov]

• Gitea Version: 1.6.4
• Git Version: 2.15.3
• Operating System: Alpine Linux 3.7.1

The current fork API (implemented in routers/api/v1/repo/fork.go) support forking a repo with two restrictions:

1. The forked repo name remains the same as the source repo name
2. The forked repo is owned by the API caller

My suggestion is to support a custom repo name for the forked repo, and to allow an admin user to create forks for other users.

Do you think such an extension is reasonable? Should I send a PR for this?

[strahe]

Good idea, really need it.

[6543]

... "allow an admin user to create forks for other users." -> you can use sudo header

[milichev]

@yosiov , there is a workaround:

PATCH /repos/owner/old-name

{
  "name": "new-name"
}

Interesting is that successive same requests result with

302 Found
Location: /api/v1/repos/owner/new-name

[pi3ch]

@yosiov , there is a workaround:

PATCH /repos/owner/old-name

{
  "name": "new-name"
}

Interesting is that successive same requests result with

302 Found
Location: /api/v1/repos/owner/new-name

Doesn't look like a workaround to me. It does not fork for a user and set a new name at the same time.

[realaravinth]

Hello, I'm new to the Gitea codebase but I'm willing to submit a patch for this issue.

From what I understand, the necessary plumbing is already available in the web form implementation at routers/web/pull.go.

For the API endpoint, we could respond with 409: Conflict, like the one you get when you try to create a repository with a duplicate name:

{
  "message": "The repository with the same name already exists.",
  "url": "https://git.batsense.net/api/swagger"
}

So that the user can retry their request with an optional name parameter:

curl -X 'POST' \
  'https://git.example.com/api/v1/repos/owner/myrepo/forks' \
  -H 'accept: application/json' \
  -H 'authorization: Basic xxx' \
  -H 'Content-Type: application/json' \
  -d '{
"name": "forkOf-myrepo"
}'