Parse the severity if the output is from shellcheck #153
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
|
🏷️ [bumpr] Next version:v1.62.1 Changes:v1.62.0...reviewdog:massongit-patch-2 |
|
🏷️ [bumpr] Next version:v1.63.0 Changes:v1.62.0...reviewdog:massongit-patch-2 |
|
so this should resolve #152 right? thanks!! |
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.
I fix to parse the severity of shellcheck output like the one above and add it to the beginning of the output, and then pass it to reviewdog.
This diff allows reviewdog to understand the severity of shellcheck.
The default severity is error.