Closed marinmo closed 3 months ago
Hmm, I wonder if this is a change on GitHub's side. The wizard does not do changes to the package visibility currently.
Need to test with manual repo creation to see if the issue persists.
This seems to be an issue on GitHubs side. This issue should be briefly mentioned in our documentation, though,
Thank you for the follow up. Yeah, might be good to add a small note somewhere in the documentation. My suggestion would be in the how-to, perhaps add a step 9 instead of the current one (so moving the current one to 10). Want me to do a PR on this?
You can PR if you want to do it, or want this done quicker.
Steps to fix:
This should be added to the troubleshooting page and mentioned on the repo creation page. Possibilities of automating this in the action should also be investigated.
Hello,
I created a new repository going through the wizard. Once done, I tried to pull my package. This failed as such;
After some troubleshooting, I realised the package created is marked as private. This means one has to add their github credentials to podman before pulling the resulting container image. This was not so with startingpoint when creating a repo via podman. Is setting packages as private intended behaviour? If so, I really think it should be made clearer in the documentation.
To make sure I didn't do a whoopsie, here's a test repo I made to reproduce the issue. I made no changes what so ever to this repo since creating it. Pulling the image also fails, if you want to try;
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/marinmo/test-image:latest
Manual solution is to set visibility for the package to public (click the package -> Package settings -> scroll down to "Danger Zone" and set visibility to public) but I can't help but to think there ought to be a better way which I'm not aware of. :)
Thanks in advance for your consideration!