Were you able to resolve this? I'm having the same problem attempting to push a ruby gem
Make sure you correctly specified repository url, as in
I got this working by adding this to my nuspec file
<repository type="git" url="https://github.com/user-name/repo-name" />
You can also specify it on the command line (dotnet or MSBuild) using `-p:RepositoryUrl=`
Hitting the same issue when publishing a .NetCore2.1 library from Windows command line.
C:\TestProject>nuget push source\TestProject.Core.Domain\bin\Release\TestProject.Core.Domain.220.127.116.11.nupkg -Source "github" WARNING: No API Key was provided and no API Key could be found for 'https://nuget.pkg.github.com/ABCCorp'. To save an API Key for a source use the 'setApiKey' command. Pushing TestProject.Core.Domain.18.104.22.1684-alpha.nupkg to 'https://nuget.pkg.github.com/ABCCorp'... PUT https://nuget.pkg.github.com/ABCCorp/ WARNING: The expected resource was not found. NotFound https://nuget.pkg.github.com/ABCCorp/ 1820ms Response status code does not indicate success: 404 (Not Found).
Have followed advice in every post/example I can find.
Using a Personal Access Token with repo, write:packages, read:packages and delete:packages scope.
Have tried using a nuget.config file, and adding source on command line.
Project file specifies the RepositoryURL, PackageId, RepositoryType, Company, Version etc.
Really can't see why this wouldn't work.
I found a fix for this, I triple checked I had all my names set correct per the GitHub documentation and nothing worked...finally I decided to pull dotnet out of the equation and just a nuget push....voila, it worked like a champ! Try your push command without the dotnet prefix.....