-
Notifications
You must be signed in to change notification settings - Fork 99
[WIP] Experiment on getting GitHub Packages packages correct casing #1855
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
Draft
o-l-a-v
wants to merge
4
commits into
PowerShell:master
from
o-l-a-v:fix-1446-github-packages-lowercase
Draft
[WIP] Experiment on getting GitHub Packages packages correct casing #1855
o-l-a-v
wants to merge
4
commits into
PowerShell:master
from
o-l-a-v:fix-1446-github-packages-lowercase
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@o-l-a-v
o-l-a-v
requested review from
SydneyhSmith,
adityapatwardhan,
alerickson and
anamnavi
as code owners
August 11, 2025 09:49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
PR Summary
Just experimenting on getting correct casing of GitHub Packages packages.
Far from done, just an idea on how one could get correct casing on GitHub Packages NuGet v3 packages.
It builds, and I've tested it against NuGet organization package
NuGet.Internal.GithubIssueTagger:See verbose line about pckName vs actual name of nuspec file.
The API returns package ID as lowercase (see #1446 (comment)), so the idea is to extract the
.nupkgand get info from its' content.So, we can work around / mitigate / fix the casing of the install path this way, but the output from
Find-PSResourcewill be lowercase, because that's what the API returns.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.