You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Levels for repo transfer
We tested Contributor access in the target org and it worked. Which makes sense, because a contributor can create a new repo.
* Update docs/hub/repositories-settings.md
Copy file name to clipboardExpand all lines: docs/hub/repositories-settings.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -10,18 +10,18 @@ You can choose a repository's visibility when you create it, and any repository
10
10
11
11
## Renaming or transferring a repo
12
12
13
-
If you own a repository, you will be able to visit the **Settings** tab to manage the name and ownership. Note that there are certain limitations in terms of use cases.
13
+
If you own a repository, you will be able to visit the **Settings** tab to manage its name and transfer ownership. Transferring or renaming a repo will automatically redirect the old URL to the new location, and will preserve download counts and likes. There are limitations that depend on [your access level permissions](./organizations-security).
14
14
15
15
Moving can be used in these use cases ✅
16
-
- Renaming a repository within same user.
17
-
- Renaming a repository within same organization. The user must be part of the organization and have "write" or "admin" rights in the organization.
18
-
- Transferring repository from user to an organization. The user must be part of the organization and have "write" or "admin" rights in the organization.
19
-
- Transferring a repository from an organization to yourself. You must be part of the organization, and have "admin" rights in the organization.
20
-
- Transferring a repository from a source organization to another target organization. The user must have "admin" rights in the source organization **and**either "write" or "admin" rights in the target organization.
16
+
- Renaming a repository within the same user.
17
+
- Renaming a repository within the same organization. You must have "write" or "admin" rights in the organization.
18
+
- Transferring repository from user to an organization. You must be a member of the organization and have "contributor" rights, at least.
19
+
- Transferring a repository from an organization to yourself. You must have "admin" rights in the organization.
20
+
- Transferring a repository from a source organization to another target organization. You must have "admin" rights in the source organization **and**at least "contributor" rights in the target organization.
21
21
22
-
Moving does not work for ❌
22
+
Moving does not work in the following cases ❌
23
23
- Transferring a repository from an organization to another user who is not yourself.
24
-
- Transferring a repository from a source organization to another target organization if the user does not have both "admin" rights in the source organization **and**either "write" or "admin" rights in the target organization.
24
+
- Transferring a repository from a source organization to another target organization if the user does not have both "admin" rights in the source organization **and**at least "contributor" rights in the target organization.
25
25
- Transferring a repository from user A to user B.
26
26
27
27
If these are use cases you need help with, please send us an email at **website at huggingface.co**.
@@ -33,4 +33,4 @@ You can disable all discussions and Pull Requests. Once disabled, all community
0 commit comments