PowerShell / PowerShell/PSResourceGet

Make it possible to include repository url and type in generated nuspec file

Open
#1,624 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Publish feature_request Needs-Attention :wave:
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Summary of the new feature / enhancement

It should be possible somehow in the Publish-PSResource cmdlet to have the repository element with attributes type and url defined in the generated Nuspec file in order to link a package to a repository in GitHub during publishing of a package. Similar to how RepositoryUrl is used when pushing a package with the dotnet cli and a csproj file.

As far as I can tell, this linking of a package to a repository must be done manually after publishing a package today.

References:
https://docs.github.com/en/enterprise-server@3.10/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry

https://devblogs.microsoft.com/nuget/introducing-source-code-link-for-nuget-packages/

Proposed technical implementation details (optional)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Publish-PSResource cmdlet to the code that generates the Nuspec file. Review how package metadata is assembled, then determine how the repository element's type and url attributes should be supplied. Done means a published package can include the requested repository metadata and the relevant existing tests pass or are updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.