✨ Use RepoClient API for Fuzzing #855
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 c1b9a6daf0df816944aa5e805df322f9a96e2a47 |
azeemshaikh38
force-pushed
the
azeems/api
branch
from
c1b9a6d
to
04d85e2
Compare
inferno-chromium
approved these changes
Aug 13, 2021
|
Integration tests success for 04d85e25b1ef5220d0cd180996cc60a4469ff1ec |
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 Fuzzing check to use RepoClient API.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.