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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
qltysh/qlty-action 0814173ae3b13074fc896ca0e8e6d631c8352509 release💡 Result:
I couldn’t find any qltysh/qlty-action tag/release that points to commit
0814173ae3b13074fc896ca0e8e6d631c8352509.The repo’s published releases/tags currently point to other commits (e.g., v2.2.0 →
a192421on Aug 11, 2025), and0814173…does not appear in the tag list—so it’s likely an untagged commit (i.e., not an official release). [1], [2]Sources:
[1] https://github.com/qltysh/qlty-action/tags
[2] https://github.com/qltysh/qlty-action/releases/tag/v2.2.0
Use a tagged release for qlty-action instead of an untagged commit.
The digest
0814173ae3b13074fc896ca0e8e6d631c8352509does not correspond to any official release in the qltysh/qlty-action repository—it's an untagged commit. Use a stable release tag likev2.2.0instead to improve auditability and reproducibility.🤖 Prompt for AI Agents