fix: Requirement Based Detectors to return right description #2127
Conversation
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
henchaves
changed the title
kevinmessiaen
approved these changes
Mar 19, 2025
…r-get_issue_description-in
|
henchaves
deleted the
feature/gsk-4238-return-right-description-for-get_issue_description-in
branch
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.
Description
Some detectors are just returning a placeholder as description instead of the real description. This PR fixes the
get_issue_descriptionfrom these detectors to return the whole description.Example:
LLMHarmfulContentDetectorLLMStereotypesDetectorRelated Issue
GSK-4238 (available on Linear)
Type of Change