Issue with owner/repo packages
See original GitHub issueSo, I was trying a package saved as owner/repo: https://github.com/nodejs/nodejs.org/commit/654e9915c0d1b8c7db92e0c2e39b6836b10e73fe
This doesn’t pass with allowed host github, npm
, but shouldn’t it pass?
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
About permissions for GitHub Packages
Permissions for repository-scoped packages. Visibility and access permissions for container images. About scopes and permissions for package registries.
Read more >The Dark Side Of Package Repositories: Ownership Drama ...
How ownership of a package in such a repository is managed depends on the specific software repository, with the especially well-known ...
Read more >Installing packages from github npm registry - auth error 401
Replace OWNER with the name of the user or organization account that owns the repository containing your project. registry=https://npm.pkg.
Read more >packages Archives | The GitHub Blog
Previously, the original publisher of a package in GitHub Packages had the owner attribute, which granted them admin privileges for the package.
Read more >Migrate NuGet Packages to GitHub Packages - josh-ops
Migrating NuGet packages stored in GitHub Packages from one ... out the GitHub repository mapping for each package in the form of owner/repo....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Done, see #63
@XhmikosR I agree. Can you open a new issue for us to discuss this and some solutions we can think of?