# Transferring a repository

A repository can be transferred to another person or an organization — together with issues, pull requests, subscribers and webhooks. Old addresses lead to the new place.

> **Who can use this:** The repository owner; for an organization's repository — an organization owner.

## Transfer

1. **Settings → Delete and transfer → Transfer this repository**.
2. Enter **to whom**: a user or organization name.
3. To confirm, type the repository name and press **Transfer**.

* **To an organization** where you may create repositories, the repository moves at once.
* **To a person** an offer is sent: an email and a line in their **Settings → Repositories**. The
  transfer happens when they press **Accept**. Without an answer the offer expires after a day.
  While it waits, you can **withdraw** it in the same danger zone.

A transfer is impossible if the new owner already has a repository with the same name — rename one
of them first — or has run out of room for new repositories.

## What moves

Files and the whole history, issues and pull requests, labels and milestones, subscribers,
releases, webhooks and members with their rights. Teams of the former organization are detached:
they belong to the organization, not to the repository.

The former owner loses access unless they are a member of the repository or can see it as public.
The new owner can give them rights under [members](https://skillok.org/docs/en/repositories/settings/collaborators).

## Old addresses

Links to the old address — pages, `git clone`, `git push` — lead to the new place until the former
owner gets a repository with the same name. It is still better to update the address on your
machines:

```bash
git remote set-url origin https://skillok.org/git/new-owner/name.git
```

---

https://skillok.org/docs/en/repositories/settings/transferring-a-repository