Skip to content

Conversation

JamesWTruher
Copy link
Contributor

Because we are using a direct invocation of ConvertTo-SecureString it triggers a warning by MS tools that secrets are not allowed to be checked in to our repository. This suppresses this warning.

PR Summary

PR Checklist

Because we are using a direct invocation of ConvertTo-SecureString it triggers a warning by MS tools that secrets are not allowed to be checked in to our repository. This suppresses this warning.
@JamesWTruher JamesWTruher self-assigned this Apr 2, 2019
@JamesWTruher JamesWTruher requested a review from TravisEz13 April 2, 2019 22:08
@JamesWTruher JamesWTruher merged commit c7e9e5c into PowerShell:development Apr 2, 2019
@JamesWTruher JamesWTruher deleted the suppressWarning001 branch April 2, 2019 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants