-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use relative URLs in dotnet push #10157
Comments
I believe this is a duplicate of the following. Please let me know if you disagree. |
@donnie-msft I think you duped the wrong one here. #4393 is not the same issue here IMO. This is about relative paths. |
added simple repro steps |
I'm going to follow up with Tim and open new issues for some weird docs issues in |
One report so far, so setting to Priority 3. |
Details about Problem
I’m trying to use
dotnet nuget push
with *.nupkg and 1) the docs are wrong (I submitted a bug) 2) the source parameter seems to require a fully-qualified source and cannot use relative roots?I’m doing this in CI and am trying to basically use “.” As the source directory but looks like the CLI treats this as too literally and doesn’t like that.
From conversation it appears it could be
https://github.com/NuGet/NuGet.Client/blob/65abcc61f73ab3d87928495f789ec74011edde7f/src/NuGet.Core/NuGet.Commands/Utility/PackageSourceProviderExtensions.cs#L47
Versus using
RelativeOrAbsolute
Repro Steps
dotnet nuget push . *.nupkg
The text was updated successfully, but these errors were encountered: