ci: Add gosec security test to workflow #42
+33
−5
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
lcbm
approved these changes
Feb 4, 2021
Fix a security error where the fuction "Stop()" would end before the AMQP channel could properly close.
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.
Describe what this PR introduces:
This patch adds a GO security check to GitHub Actions "Build and Test" workflow. This check is made using the gosec tool,
you can get more information visiting its repository: Gosec
What kind of change does this PR introduce? (check at least one)
Does this PR introduce any breaking changes? (check one)
If yes, please describe the impact and migration path for existing applications:
In this repository code current state it will not pass the security test.
The PR fulfills these requirements:
fix #xxx[,#xxx], where "xxx" is the issue number)Testing environment:
If you have relevant logs, error output and etc, please attach them.
Other information: