How can I make packages I publish visible to other organization members by default?

[marcel-22]

Select Topic Area

Question

Body

Hi,

We use GitHub Packages to publish private npm packages to our organization account. Our organization account has no repositories, just packages. The Git repositories are archived in Atlassian's Bitbucket.

When a new package is published to GitHub for the first time, it is not visible to other members of the organization by default. We have to manually configure access via the package settings and 'invite' (add) each member individually and change the role to 'Write' in order for this user to be able to make and publish changes.

How can we configure GitHub Packages in such a way that when any organization member creates a new package it will automatically be visible to other organization members as well? Note: We do not have any repositories in GitHub. And packages are always private.

I found a related discussion here, but this does not answer my question.

Any help would be greatly appreciated!

[dmarx]

set the package permission to internal instead of private

[ebndev]

Hi @dmarx, thanks for taking the time to answer!

@marcel-22 if the response above helped, please feel encouraged to mark it as the answer. If not, let us know if you have further questions or post the solution if you've resolved it on your own. It would be helpful for other users who might experience this in the future 😄

[marcel-22]

Hi, thanks! I can't believe I missed this. I was so focused on public and private that I didn't even notice internal. 👍