Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Allow including source control metadata in Publish-Module #576

Closed
davidroberts63 opened this issue Jan 27, 2020 · 2 comments
Closed

Allow including source control metadata in Publish-Module #576

davidroberts63 opened this issue Jan 27, 2020 · 2 comments

Comments

@davidroberts63
Copy link

Is it reasonable to allow Publish-Module to include source control metadata? That is the following:

  • type (git|tfs|svn|etc...)
  • url
  • branch
  • commit

The nuspec allows for including this metadata in the nuspec.

If so, I've two overall ideas.

  1. Pull this data from the PSData, in a similar manner as the LicenseUri.
    This would require changes to New-NuSpecFile and Publish-PSArtifactUtility. And I think that's all. Developers would have to find their own process for injecting that into their PSData, however if they are using CI/CD process then they may be able to do this within a reasonable amount of effort.
  2. Allow this to be specified as a parameter to Publish-Module.
    This would require changes to the same functions as above, along with Publish-Module itself. Though this option would be easier for a CI/CD process to integrate with.

I also have a third idea, but that is allowing developers to specify their own nuspec and adjusting as needed during the Publish-Module process. However I think the changes that would require would be too large. But I wanted to mention it as an idea.

@ThomasNieto
Copy link
Contributor

PowerShellGet is currently being redesigned. You should place your comment in PowerShell/PowerShell-RFC#237 for your feature be heard.

@davidroberts63
Copy link
Author

Will do. Thank you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants