gt-repo-transfer1

Usage

Overview

Transfer a repository to another user or organization. --team grants teams of a new owning organization access to it.

Gitea completes the transfer at once when you may create repositories for the new owner, such as in an organization you can create repositories in. Otherwise the transfer waits until the new owner accepts it on the repository's page, and the repository keeps its owner until then.

actions_enabled, archived, clone_url, default_branch, description, empty,
fork, forks_count, full_name, id, mirror, mirror_interval, name,
open_issues_count, open_pr_count, original_url, parent, private, ssh_url,
stars_count, template, topics, transfer_pending, updated_at, url, website

Options

-h, --help[=false]
help for transfer

--team=[]
Grant this team of the new owning organization access (repeatable)

Options inherited from parent commands

--csv[=""]
Output CSV with the specified comma-separated fields, or all fields

--cwd=""
Working directory for repository discovery

--debug[=false]
Log the method, URL, status, and duration of each HTTP request to stderr

--host=""
Gitea instance URL, including any base path

--interactive[=false]
Allow prompts with machine output

-q, --jq=""
Filter JSON output using a jq expression; implies --json

--json[=""]
Output JSON with the specified comma-separated fields, or all fields

--no-input[=false]
Disable prompts and implicit editor/browser interactions

--remote=""
Git remote used for repository discovery

-R, --repo=""
Select a repository as OWNER/REPO or URL

--sudo=""
Perform API requests as this user (requires an administrator account)

--user=""
Account name on the selected instance

-y, --yes[=false]
Accept confirmations without prompting

Examples

# Transfer the repository of the current clone to an organization
$ gt repo transfer acme --team developers
# Offer another repository to a user
$ gt repo transfer bob -R alice/project