Skip to content

feat(seer): Thread autofix_automation_tuning into night shift's triage payload#120386

Draft
trevor-e wants to merge 2 commits into
masterfrom
telkins/night-shift-automation-tuning
Draft

feat(seer): Thread autofix_automation_tuning into night shift's triage payload#120386
trevor-e wants to merge 2 commits into
masterfrom
telkins/night-shift-automation-tuning

Conversation

@trevor-e

Copy link
Copy Markdown
Member

Night shift never told Seer about a project's sentry:autofix_automation_tuning setting, so its triage prompt couldn't calibrate autofix selectivity per project — a project configured super_low (only autofix near-certain fixes) was triaged identically to one configured always.

Threads each eligible project's automation_tuning value through EligibleProject -> _dispatch_to_seer_feature -> _build_triage_payload onto TriageCandidate, gated to legacy (non-seat-based) orgs — seat-based orgs always send None, reusing the same is_legacy_org check already used for the autofix rate limit.

Pairs with getsentry/seer#7473, which adds the corresponding per-candidate field and prompt section on the Seer side (recommended to land first, since it's fully backward-compatible either way).

…e payload

Night shift never told Seer about a project's sentry:autofix_automation_tuning setting, so its triage prompt couldn't calibrate autofix selectivity per project. Pairs with getsentry/seer#7473, which adds the corresponding per-candidate field and prompt section.

Threads each eligible project's automation_tuning value through EligibleProject -> _dispatch_to_seer_feature -> _build_triage_payload onto TriageCandidate, gated to legacy (non-seat-based) orgs -- seat-based orgs always send None, reusing the same is_legacy_org check already used for the autofix rate limit.
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 22, 2026
The comments restated the field name/type or downstream usage already evident from the code a few lines below; kept only the non-obvious behavioral note (None for seat-based orgs regardless of the project's own setting).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants