Levels for repo transfer #1850
Merged
Levels for repo transfer #1850
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We tested Contributor access in the target org and it worked. Which makes sense, because a contributor can create a new repo.
pcuenca
commented
Jul 28, 2025
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
pcuenca
commented
Jul 28, 2025
Comment on lines
+19
to
+20
| - Transferring a repository from an organization to yourself. You must have "admin" rights in the organization. | ||
| - 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. |
Member
Author
There was a problem hiding this comment.
I didn't verify if write is enough for the source org (I think it should, as users with write access are able to delete any repo in the org).
pcuenca
commented
Jul 28, 2025
| - 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. | ||
| - Renaming a repository within the same user. | ||
| - Renaming a repository within the same organization. You must have "write" or "admin" rights in the organization. | ||
| - Transferring repository from user to an organization. You must be a member of the organization and have "contributor" rights, at least. |
Member
Author
There was a problem hiding this comment.
This worked for a test we did in transformers-community.
Vaibhavs10
approved these changes
Jul 29, 2025
Member
Vaibhavs10
left a comment
Vaibhavs10
left a comment
There was a problem hiding this comment.
Nice! Thanks a lot for the updates! Let's maybe get @Kakulukian/ someone from the hub team to review this as well before we merge 🙏
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We tested Contributor access in the target org and it worked. Which makes sense, because a contributor can create a new repo.
cc @gante @Vaibhavs10