feat(autofix): pin base shas via prompt metadata#117956
Open
joseph-sentry wants to merge 4 commits into
Open
Conversation
depends on getsentry/seer#7006 gonna use the new method for pinning base shas from that PR
github-actions
Bot
added
the
Scope: Backend
joseph-sentry
changed the title
Zylphrex
approved these changes
Jun 18, 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
2 participants
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.
depends on https://github.com/getsentry/seer/pull/7006
gonna use the new method for pinning base shas from that PR
we want to pin the commit sha at the code changes step since we want to avoid having diff between the code changes patch and the revision against which we will open the PR
the ideal future state is that we will merge from main before making subsequent code changes / PR iterations
Fixes https://linear.app/getsentry/issue/CW-1459