Repository navigation
Fix credential scan issues - #4927
Merged
Travis Plunk (TravisEz13) merged 2 commits intoSep 27, 2017
Merged
Travis Plunk (TravisEz13) merged 2 commits into
Travis Plunk (TravisEz13) merged 2 commits into
Conversation
Travis Plunk (TravisEz13)
requested review from
Aditya Patwardhan (adityapatwardhan) and
Dongbo Wang (daxian-dbw)
September 26, 2017 23:20
Travis Plunk (TravisEz13)
requested review from
Hemant Mahawar (HemantMahawar),
Steve Lee (SteveL-MSFT) and
Joey Aiello (joeyaiello)
as code owners
September 26, 2017 23:20
Aditya Patwardhan (adityapatwardhan)
requested changes
Sep 27, 2017
| @@ -1,8 +1,9 @@ | |||
| Describe "ConvertTo-SecureString" -Tags "CI" { | |||
| Describe "ConvertTo--SecureString" -Tags "CI" { | |||
There was a problem hiding this comment.
Seems to have an extra - between ConvertTo and SecureString
Member
Author
There was a problem hiding this comment.
I have to rename it to something other than convertto-securestring.
| Describe "ConvertTo--SecureString" -Tags "CI" { | ||
|
|
||
| Context "Checking return types of ConvertTo-SecureString" { | ||
| Context "Checking return types of ConvertTo--SecureString" { |
There was a problem hiding this comment.
Seems to have an extra - between ConvertTo and SecureString
Member
Author
There was a problem hiding this comment.
See the previous comment
Travis Plunk (TravisEz13)
removed request for
Hemant Mahawar (HemantMahawar) and
Joey Aiello (joeyaiello)
September 27, 2017 17:44
Aditya Patwardhan (adityapatwardhan)
approved these changes
Sep 27, 2017
Merged
Contributor
|
Just out of curiosity, is the |
Member
Author
|
Sebastian N. (@megamorf) It's specific to the tool we use. Unfortunately, the tool itself is internal to Microsoft only. That is why we run it in VSTS and not our normal CI systems. |
Contributor
|
Travis Plunk (@TravisEz13) Ah, that makes sense. Thanks for the answer :-) |
Thatgfsj (Thatgfsj)
pushed a commit
to Thatgfsj-contribs/PowerShell
that referenced
this pull request
Aug 6, 2026
* Add file secret suppression * Add line secret suppression * This will be consumed in the VSTS daily build. * Renamed tests with ConvertTo-SecureString to avoid false positives
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add suppression for lines with secrets.
Add suppressions for files which are secrets.
This will be consumed in the VSTS daily build.
Renamed tests with
ConvertTo-SecureStringto avoid false positives