Add automated issue verification/triaging workflow#1019
Merged
Conversation
vjovanov
approved these changes
Mar 3, 2026
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
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.
What does this PR do?
In this PR we introduce the
new-issue-verification.ymlworkflow, which verifies newly-createdlibrary-new-requestissues are not created for artifacts that are already supported either by the reachability metadata repo or frameworks (listed inmetadata/library-and-framework-list.json), and if they are, automatically closes them with an informative message. The issues can be re-opened without rerunning the workflow if the issue author believes that the automated closure is a mistake.The workflow verifies 3 separate points:
<groupId>:<artifactId>:<version>format, the issue is closed with a suggestion to open an issue with the correct format (example),check-library-support.sh), the issue is closed (example),metadata/library-and-framework-list.json, the issue is closed (example).Fixes: #945