-
Notifications
You must be signed in to change notification settings - Fork 61.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclear if transfer repo and associated redirect applies to releases #1941
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Ooh, that's an interesting one @RoxaBee thanks for opening an issue! I'll need to ask around and find out the answer. I'll report back when I figure it out 👀 |
@RoxaBee I just checked in with engineering and they confirmed that releases are transferred with everything else! Since almost everything is included in a transfer, I think we'll keep documenting the exceptions instead of explicitly calling out releases as being included. I'm going to close this out now, thanks for contributing! 💖 |
Thanks @janiceilene ! |
Thanks Roxana! @janiceilene Noting that we could also add some language about what happens to GitHub Packages in the repo ownership transfer to our doc 👍 |
@glennwester Could you open an issue in docs-content outlining what happens and we can figure out how to best incorporate that into the docs? Thank you! |
Hi @janiceilene maybe easier to just reopen the issue? @glennwester learned that the packages in the GitHub Package Registry are transferred along with the repository and are subsequently only available at the new repository location. There is no forward so not quite the same and maybe should be called out. |
Thanks @RoxaBee! I think we're going to look at updating the package docs internally with some other work we're doing ⚡ |
What article on docs.github.com is affected?
https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/transferring-a-repository
What part(s) of the article would you like to see updated?
Include something on what happens to releases when a repo is transferred from account/organization to another. Will the releases be transferred along with issues, in-flight pr, etc. Also will the redirect apply to releases as well?
Additional information
The text was updated successfully, but these errors were encountered: