Repository navigation
Conversation
billyvg
reviewed
Oct 23, 2026
This was referenced Oct 23, 2026
wedamija
force-pushed
the
danf/inv-fu-18-update-detector-dry-run
branch
from
October 23, 2026 23:28
8c92f3b to
9566cb0
Compare
wedamija
force-pushed
the
danf/inv-fu-16-apply
branch
from
October 23, 2026 23:28
8189800 to
132da5c
Compare
wedamija
added a commit
that referenced
this pull request
Oct 23, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This applies a suggested monitor change as the user who clicked, through the detector validator, or only checks it on a dry run. If someone changed the monitor after Seer made the suggestion, nothing is applied, and the user sees which settings moved. Depends on #128681
wedamija
added a commit
that referenced
this pull request
Oct 23, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save. Depends on #128681 and #128723
Contributor
Sentry Snapshot Testing
|
wedamija
force-pushed
the
danf/inv-fu-18-update-detector-dry-run
branch
from
October 24, 2026 01:10
9566cb0 to
87799ce
Compare
wedamija
force-pushed
the
danf/inv-fu-16-apply
branch
from
October 24, 2026 01:10
132da5c to
36395e9
Compare
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This applies a suggested monitor change as the user who clicked, through the detector validator, or only checks it on a dry run. If someone changed the monitor after Seer made the suggestion, nothing is applied, and the user sees which settings moved. Depends on #128681
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save. Depends on #128681 and #128723
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This applies a suggested monitor change as the user who clicked, through the detector validator, or only checks it on a dry run. If someone changed the monitor after Seer made the suggestion, nothing is applied, and the user sees which settings moved. Depends on #128681
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save. Depends on #128681 and #128723
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an endpoint that applies a suggested action request as the current user, or with dryRun only checks whether it would apply. Each action kind does its own checks and change, so the endpoint works the same for every kind. Depends on #128680
Kinds now only make the change: they return what the activity feed shows, or raise when the action is stale or invalid, and the shared apply path updates the request. Error codes are typed, the endpoint picks the status, and a dry run rolls back whatever it touched.
wedamija
force-pushed
the
danf/inv-fu-18-update-detector-dry-run
branch
from
October 24, 2026 03:49
87799ce to
1d4f218
Compare
wedamija
force-pushed
the
danf/inv-fu-16-apply
branch
from
October 24, 2026 03:49
5e558ca to
52db83c
Compare
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This applies a suggested monitor change as the user who clicked, through the detector validator, or only checks it on a dry run. If someone changed the monitor after Seer made the suggestion, nothing is applied, and the user sees which settings moved. Depends on #128681
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save. Depends on #128681 and #128723
wedamija
added a commit
that referenced
this pull request
Oct 24, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. This adds an Apply button to a suggested monitor change. When the card shows, it asks the backend with a dry run whether the change would apply, and says why when it can't, so the user only clicks a change that will save. Depends on #128681 and #128723
This branch was successfully deployed
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.
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.
This adds an endpoint that applies a suggested action request as the current user, or with dryRun only checks whether it would apply. Each action kind only checks and makes its change, and the shared path records what happened, so the endpoint works the same for every kind.
Depends on #128680