🐛 Use RepoClient.Search API in SAST check #857
Merged
Conversation
This file contains 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
|
Integration tests success for d11548493bc137e2127b350c7b85478eedf3fa27 |
azeemshaikh38
force-pushed
the
azeems/api
branch
2 times, most recently
from
a698846
to
744da4a
Compare
|
Integration tests failure for a698846908f14b15a683d737438cecb3cd58a830 |
|
Integration tests success for 744da4a7baef9a160ee3438e1a52b97874d0322a |
inferno-chromium
approved these changes
Aug 16, 2021
azeemshaikh38
force-pushed
the
azeems/api
branch
from
744da4a
to
a9e53ad
Compare
|
Integration tests success for a9e53adbb0337bed894dfc3ddf7fb4f17b6a6ec4 |
azeemshaikh38
force-pushed
the
azeems/api
branch
from
a9e53ad
to
ffd9d2f
Compare
|
Integration tests success for ffd9d2fed255d5fadd663313e09d12232fe67625 |
|
Integration tests success for a21947e97c961ee31c94580829aef505a2475e8d |
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Update SAST check to use the new RepoClient.Search API.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.