feat: add endpoint to list only issues that have PRs created from Seer Explorer by billyvg · Pull Request #107850 · getsentry/sentry

billyvg · 2026-02-09T16:08:22Z

This exposes the endpoint on Seer and joins the results from Seer with serialized groups.

This will be used internally only for now for our macos app.

github-actions · 2026-02-09T20:17:27Z

🚨 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 #discuss-dev-infra channel.

linear · 2026-02-09T22:55:22Z

AIML-2455 Loading issues is slow pt. 2

billyvg · 2026-02-10T21:38:06Z

src/sentry/seer/endpoints/organization_seer_explorer_pr_groups.py

+        Get a list of issues that have a PR created from Seer Explorer
+
+        Query Parameters:
+            None


I may add one to filter for current user only, not sure yet

nit - could maybe pass in the category_key + value?

@aliu39 I can take a look as a follow-up. when Seer Explorer creates a PR outside of an issue, is category_key still autofix? (trying to better understand how cat key/value is used)

yeah PRs created by the floating explorer chat have category_key = None. categ is set on SeerExplorerClient init and that's saved to the ExplorerState + DbExplorerRun in seer

if ppl make more explorer-based features in the future, they can set other categs on their client

billyvg · 2026-02-10T21:38:53Z

src/sentry/seer/explorer/client.py

        limit: int | None = None,
-    ) -> list[ExplorerRun]:
+        expand: Literal["prs"] | None = None,
+        only_current_user: bool = True,


/explorer-runs/ requires that it filters for current user only.

src/sentry/seer/endpoints/organization_seer_explorer_pr_groups.py

Rename endpoint, client method, URL path, and test file: - OrganizationExplorerIssuesWithPRs -> OrganizationSeerExplorerPRGroups - get_issues_with_prs() -> get_pr_summaries() - /seer/explorer-prs/ -> /seer/explorer-pr-groups/ - Seer API: runs/with-prs -> pr-summaries - Fix missing user_id in test fixture helper

…ps endpoint Remove per-group dedup so all runs are returned. Allow group to be None when group_id is missing or unresolvable, and capture_message to Sentry at warning level in those cases.

armcknight

Mostly questions from reading the tests, as that is where I think my review is best left 😄

tests/sentry/seer/endpoints/test_organization_seer_explorer_pr_groups.py

armcknight · 2026-02-24T19:02:52Z

tests/sentry/seer/endpoints/test_organization_seer_explorer_pr_groups.py

+        pr_states = response.json()["data"][0]["repoPrStates"]
+        assert pr_states["getsentry/sentry"]["repoName"] == "getsentry/sentry"
+        assert pr_states["getsentry/sentry"]["branchName"] is None
+        assert pr_states["getsentry/sentry"]["prNumber"] is None
+        assert pr_states["getsentry/sentry"]["prUrl"] is None
+        assert pr_states["getsentry/sentry"]["prCreationStatus"] is None


Are there real life examples where we have a PR linked to an issue but none of this information? Or am I misunderstanding the test case?

No I think this is just based on the typing of repo_pr_states

armcknight · 2026-02-24T19:06:01Z

tests/sentry/seer/endpoints/test_organization_seer_explorer_pr_groups.py

+    def test_get_no_matching_groups_returns_null_group(self) -> None:
+        """When Seer returns group IDs that don't exist in the requested project, group is None."""
+        self.mock_client.get_runs.return_value = [self._make_seer_item(group_id=999999)]
+
+        response = self.client.get(self.url + f"?project={self.project.id}")
+
+        assert response.status_code == 200
+        data = response.json()["data"]
+        assert len(data) == 1
+        assert data[0]["group"] is None
+
+    def test_get_includes_null_group_id_runs(self) -> None:
+        """Runs without a group_id are included with group=None."""
+        group = self.create_group(project=self.project)
+
+        self.mock_client.get_runs.return_value = [
+            self._make_seer_item(group_id=group.id, run_id=1),
+            self._make_seer_item(group_id=None, run_id=2),
+        ]
+        self.mock_serialize.return_value = [{"id": str(group.id), "title": "Issue 1"}]
+
+        response = self.client.get(self.url + f"?project={self.project.id}")
+
+        assert response.status_code == 200
+        data = response.json()["data"]
+        assert len(data) == 2
+        assert data[0]["group"]["id"] == str(group.id)
+        assert data[1]["group"] is None


I don't know what group None implies, w.r.t. the native clients. Is this a response state we need to worry about, or is this just internal server logic? Looking at the client implementation, we only have this in one place, SentryIssueSummary.groupId, which is not an optional attribute, so we wouldn't be able to handle None if it came down in a response.

For native clients, we probably want to handle this case -- we can make Seer Explore runs that generate PRs that are not bound to an Issue.

hmm interesting. i guess let's see what happens, would be easy enough to fix in the clients 👍🏻

aliu39 · 2026-02-25T03:27:34Z

src/sentry/seer/endpoints/organization_seer_explorer_pr_groups.py

+        Get a list of issues that have a PR created from Seer Explorer
+
+        Query Parameters:
+            None


nit - could maybe pass in the category_key + value?

github-actions bot added Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components labels Feb 9, 2026

vercel bot deployed to Preview February 9, 2026 16:16 View deployment

vercel bot deployed to Preview February 9, 2026 20:19 View deployment

vercel bot deployed to Preview February 9, 2026 21:44 View deployment

vercel bot deployed to Preview February 9, 2026 22:57 View deployment

vercel bot deployed to Preview February 9, 2026 23:49 View deployment

billyvg changed the title ~~wip: add endpoint to list issues that have PRs to fix them~~ feat: add endpoint to list issues that have PRs to fix them Feb 9, 2026

vercel bot deployed to Preview February 10, 2026 18:37 View deployment

billyvg changed the title ~~feat: add endpoint to list issues that have PRs to fix them~~ feat: add endpoint to list only issues that have PRs created from Seer Explorer Feb 10, 2026

vercel bot deployed to Preview February 10, 2026 20:19 View deployment

billyvg force-pushed the billy/feat-seer-new-explorer-prs-endpoint branch from e2a828c to 5764824 Compare February 10, 2026 20:37

vercel bot deployed to Preview February 10, 2026 20:40 View deployment

billyvg force-pushed the billy/feat-seer-new-explorer-prs-endpoint branch from 559ac54 to 148a6a8 Compare February 10, 2026 20:42

billyvg removed the Scope: Frontend Automatically applied to PRs that change frontend components label Feb 10, 2026

vercel bot deployed to Preview February 10, 2026 20:45 View deployment

github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Feb 10, 2026

vercel bot deployed to Preview February 10, 2026 20:48 View deployment

vercel bot deployed to Preview February 10, 2026 20:52 View deployment

billyvg commented Feb 10, 2026

View reviewed changes

billyvg marked this pull request as ready for review February 10, 2026 21:39

billyvg requested review from a team as code owners February 10, 2026 21:39

billyvg requested a review from aliu39 February 10, 2026 21:40

sentry bot reviewed Feb 10, 2026

View reviewed changes

src/sentry/seer/endpoints/organization_seer_explorer_pr_groups.py Outdated Show resolved Hide resolved

cursor bot reviewed Feb 10, 2026

View reviewed changes

vercel bot deployed to Preview February 10, 2026 22:06 View deployment

sentry bot reviewed Feb 10, 2026

View reviewed changes

src/sentry/seer/endpoints/organization_seer_explorer_pr_groups.py Outdated Show resolved Hide resolved

billyvg added 19 commits February 23, 2026 15:46

update to pass project to SeerExplorerClient

9678233

wip: add endpoint to list issues that have PRs to fix them

dd06653

update to allow multi projects

f5ad906

use GroupSerializerSnuba

f058cc4

add user_id

f7fdda4

re-use get_runs

82bc746

remove old endpoint

3c6989c

improve models

2903857

consistency updates

58a2a3f

add comment for endpoint

b08dace

return empty list when no projects to be consistent with other APIs

d4bf7db

cr fixes

6d07c6a

we dont need an explicit projects check

47e7dd4

dont convert pydantic model to dict

218e1a5

category_key=autofix only and pass project_ids

250ff79

change endpoint response format

a4ca8a4

also filter runs by start/end instead of groups

910d01e

feat(seer): return all runs and allow null groups in explorer PR grou…

77cd597

…ps endpoint Remove per-group dedup so all runs are returned. Allow group to be None when group_id is missing or unresolvable, and capture_message to Sentry at warning level in those cases.

billyvg force-pushed the billy/feat-seer-new-explorer-prs-endpoint branch from cf2ef59 to 77cd597 Compare February 23, 2026 21:29

🛠️ Sync API Urls to TypeScript

728717b

vercel bot deployed to Preview February 23, 2026 21:34 View deployment

billyvg marked this pull request as ready for review February 23, 2026 22:09

billyvg requested review from Zylphrex and aliu39 February 23, 2026 22:09

armcknight reviewed Feb 24, 2026

View reviewed changes

aliu39 approved these changes Feb 25, 2026

View reviewed changes

billyvg merged commit ff12004 into master Feb 25, 2026
78 checks passed

billyvg deleted the billy/feat-seer-new-explorer-prs-endpoint branch February 25, 2026 14:40

github-actions bot locked and limited conversation to collaborators Mar 13, 2026

Uh oh!

Conversation

billyvg commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 9, 2026

Uh oh!

linear bot commented Feb 9, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aliu39 Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

armcknight left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

armcknight Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

billyvg commented Feb 9, 2026 •

edited

Loading

aliu39 Feb 25, 2026 •

edited

Loading

armcknight Feb 25, 2026 •

edited

Loading