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 Dec 7, 2021. It is now read-only.
This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.
stalebot
added
the
stale
The issue or pull request was marked as stale because there hasn't been activity from the community.
label
Feb 14, 2019
Hi @Iristyle
It's a very valid request and something we'd probably like to do across all Resources.
There are other consideration we will discuss, probably in a coming DSC Community Call, such as SemVer, and the potential use of gitversion.
I'm putting this on-hold to circumvent the stale bot, and give some time to bring this up with the rest of the community.
Feel free to @ me if you don't get a follow up by early next month.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
on holdThe issue or pull request has been put on hold by a maintainer.questionThe issue is a question.
Hi!
I see you folks have a
0.1.0
,0.2.0
and0.3.0
releases published to the PowerShell Gallery at https://www.powershellgallery.com/packages/WmiNamespaceSecurity/0.3.0, but no corresponding tags in the GitHub repo. At Puppet, we use the tags as a "source of truth" when building wrapper modules, so it would be awesome if you could push tags for the SHAs that correspond to the actual releases (as a bonus, releases will also show in https://github.com/PowerShell/WmiNamespaceSecurityDsc/releases)You can see that all of the other DSC resource repositories follow this model - for instance https://github.com/PowerShell/ComputerManagementDsc/ uses tags like
6.0.0.0-PSGallery
,5.0.0.0-PSGallery
, etc.Thanks for the consideration!
The text was updated successfully, but these errors were encountered: