Supporting other scope than the name of the GH org?

[attilah]

Select Topic Area

Question

Body

I was having hard time Today publishing a package to our organization's (npm) repository. Everything seemed to be fine but I got 403. I have read the documentation pages in the topic, but I was still stuck.

Based on a hunch I changed the scope of the npm package to our org's name and voila' it succeeded.

Is there any way to have different scopes (per product as an example) for a given GH organization?

Am I missing something, and it is supported Today just did not find a way?

Based on my understanding, once repositryUrl is specified GitHub already knows the OWNER where the package should go, so I don't see a problem why the scope could not be anything...

The error I was getting:

npm notice Publishing to https://npm.pkg.github.com/ with tag latest and default access
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://npm.pkg.github.com/<scope>%2f<package name> - Permission not_found: owner not found
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.