[to #67] fix gosec failure for BR #68
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
Signed-off-by: Jian Zhang <zjsariel@gmail.com>
zz-jason
force-pushed
the
fix/fix-br-gosec
branch
from
e1f725d
to
fff4563
Compare
zeminzhou
approved these changes
Mar 21, 2022
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.
Signed-off-by: Jian Zhang zjsariel@gmail.com
What problem does this PR solve?
Issue Number: [to #67]
Problem Description: gosec failed on BR directory
What is changed and how does it work?
the original hint which indicates gosec not to check the didn't work, changed them to a work one.
Code changes
Check List for Tests
This PR has been tested by at least one of the following methods:
Side effects
Related changes