You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
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.
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.
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.
The text was updated successfully, but these errors were encountered:
Is it reasonable to allow Publish-Module to include source control metadata? That is the following:
The nuspec allows for including this metadata in the nuspec.
If so, I've two overall ideas.
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.
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.
The text was updated successfully, but these errors were encountered: