GitHub Community
-
|
What’s the logic for packages showing up a the repo level? I have done the following:
I don’t know that it matters but our org name is Title-Cased but the image repo has to be lower-case. I also noticed that if I click |
Beta Was this translation helpful? Give feedback.
Replies: 18 comments 2 replies
-
|
Hi @ghudik-cas! The team is working on adding container images pushed to GitHub Container Registry to the repository sidebar. We should have them there soon, it’s not an issue with your organization settings. :slight_smile: |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, good to to know. Thanks @noahmatisoff |
Beta Was this translation helpful? Give feedback.
-
|
was wondering why this wasn’t working yet it showed up as successfully built |
Beta Was this translation helpful? Give feedback.
-
|
Please check again, this fix should have rolled out now. |
Beta Was this translation helpful? Give feedback.
-
|
I see it now. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Nice, thank you! It seem to work only when logged in though, if I open my test repo in a new browser instance or private window without logging in the “Packages” section say “No packages published”. I can see the package if I click through to packages anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Good to know. This logged out experience is because of how we roll out feature flags. Once the flag is removed it will become available to everyone. For now it is only for logged in users. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, that makes sense. Thanks for the explanation! 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
It looks still not working. I am not able to see the packages even though the build logs indicate a successful pushing to ghcr.io |
Beta Was this translation helpful? Give feedback.
-
|
Same. Did this regress? I can push / pull the image. But it is no where in the UI and I cannot manually get to it by name in URL. |
Beta Was this translation helpful? Give feedback.
-
|
No, still not working |
Beta Was this translation helpful? Give feedback.
-
|
I am just packaging up some JS files. I can pull it down via the |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm this is not working again with docker container registry. |
Beta Was this translation helpful? Give feedback.
-
|
Not showing up for me either. Can successfully push/pull the images to/from GCR but they're not showing up under Packages. Interestingly enough, I can see a couple images built a month ago and one built 9 days ago but nothing more recent than that. |
Beta Was this translation helpful? Give feedback.
-
|
After all the steps, it still needs to happen for generic packages. Do you have any plans to include this in the future? For instance, I'm pushing an OPA policy in the overall list of packages. It works but is not visible inside the repository despite linking. Thanks @clarkbw :) |
Beta Was this translation helpful? Give feedback.
-
|
Same for me. New repo, build and pushed image as But... I found how to fix it:
Now I can see package in repository. But to make full use of new package I also needed to add permissions for repositories so they could read/write. Lesson is that packages seems not related to repository at first creation. You need to actually attach package to repository and add permissions. Another lesson: THIS IS REALLY POOR UX. I did not even have a link in UI to package list in my repo. I tried attaching /packages to url and then I had page with links to tutorials on how to create package. Finally I managed to view all packages in my organization and then I actually saw my docker image sent hour ago... |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for providing this @piotrekkr, this resolved my issues |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue, I'm working in a private repo from an organization. I accidentally published it with a typo, instead of widgets-sdk I published widget-sdk. I fixed it and published it again, the package is being published in GitHub packages though because I can install it in other projects and it doesn't let me publish the same version. The UI is not showing it on the organization packages or the repo packages list. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @clarkbw do you know what could be the issue here? |
Beta Was this translation helpful? Give feedback.
-
|
Running into this issue ☝️ check timestamp |
Beta Was this translation helpful? Give feedback.
Please check again, this fix should have rolled out now.