fix(issues): Stop double-emitting issue activities for Seer PR created#115749
Conversation
github-actions
Bot
added
Scope: Frontend
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.55% |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit efbeca9. Configure here.
shashjar
deleted the
shashjar/stop-double-emitting-seer-PR-created-activities-on-issues
branch
… from timeline (#116233) Reverts #115749 to restore `SEER_PR_CREATED` activity creation in the Seer operator pipeline (fed by webhook events received into Sentry from Seer). Hides `SEER_PR_CREATED` activities from the frontend activity timeline on the issue details page - we continue to rely on `SET_RESOLVED_IN_PULL_REQUEST` activities for the UI display instead (to avoid duplicate "PR created" entries).
2 participants
Resolves ID-1534.
We already have issue activity recording in place for Seer Autofix PRs created via our GitHub webhook, so we can remove the creation logic for this redundant activity type.