Open
Conversation
Author
|
I cannot add labels myself, can you add |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
✨ What's this?
Add some metadata for the NuGet gallery (https://www.nuget.org/packages/Bearded.Utilities).
Specifically, a link back to the github repo, a MIT licence and a good description.
🔍 Why do we want this?
More clarity for people using the NuGet gallery.
🏗 How is it done?
Mostly moving metadata from the (no longer used) nuspec file to the project file, as is the best practice these days (https://learn.microsoft.com/en-us/nuget/create-packages/package-authoring-best-practices).
🔬 Why not another way?
It's best practice these days to use the project file instead of nuspec files (which you weren't using anymore anyways).
🦋 Side effects
Maybe the tags aren't up to date anymore?