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
We recently migrated a project from an individual account to an organization through the Project Settings page. The transfer left the existing Docker Images in the individual account without a repo attached to them instead of transferring them to the new Org. Now when users do a pull they get an image that's several weeks old unless they change the image name.
Why isn't gchr.io redirecting pull requests when a project gets transferred to an Organization?
Why isn't the transfer project functionality moving current packages to the new location?
PackagesHost your dependencies, libraries, and production-ready code, right from your repository
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Bug
Body
We recently migrated a project from an individual account to an organization through the Project Settings page. The transfer left the existing Docker Images in the individual account without a repo attached to them instead of transferring them to the new Org. Now when users do a pull they get an image that's several weeks old unless they change the image name.
Beta Was this translation helpful? Give feedback.
All reactions