Repository navigation
Conversation
Patai5
approved these changes
Oct 26, 2026
Patai5
left a comment
Patai5
left a comment
Contributor
There was a problem hiding this comment.
Super cool 🚀 Honestly this action is pretty overpowered right now :)) I'm very pleased with it! Thank you!
…the bug Define potentially affected runs by whether an input could trigger the bug when rerun, including content-dependent and rare-input cases, and keep every Impact metric on the same point of view, one sub-section per view. Let flakiness runs try other inputs and report the rate per input, and base the priority on the most impactful view. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gate-impact Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
foxt451
changed the title
foxt451
marked this pull request as ready for review
October 30, 2026 14:18
foxt451
requested review from
JuanGalilea,
metalwarrior665 and
ruocco-l
as code owners
October 30, 2026 14:18
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.
Closes #208
Brings the metrics Nika asked for regarding impact. As a final step claude will also preliminarily set priority field so we can pre-sort issues during grooming meetings.
Test issue https://github.com/apify-store/tiktok/issues/1544. I did a couple of iterations here but this one I think is okay: it assesses impact from two points of view, recognizes that the bug manifests only in a handful of profiles and correctly picks the most important point of view to set prio. (won't deny I might've overfit the prompt to this issue in one place but we'd see better during use)
Lukáš said it's fine to keep redash stuff in this repo since we'd move the claude stuff away anyways in the future