Conversation
maritiren
reviewed
Sep 14, 2026
maritiren
left a comment
maritiren
left a comment
There was a problem hiding this comment.
I've rebased on main and tested this, but I am wondering whether the DESC_TEMPLATE (see TOOL_NAME at the bottom of the image) is the right way to put this?
Is maybe a label a better place to put it? Any thoughts?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Because multiple tools can be used to report to Code Scanning Alerts, I wanted a way to identify which one has been used while being added to Jira.
This feature adds TOOL_NAME= in Jira's description field.
It gathers this information from each ["tool"]["name"] GitHub alert properties.
ie: TOOL_NAME=ZAProxy, TOOL_NAME=CodeQL, etc.