Skip to content

feat(issues): Link commit activities to pull requests#119373

Draft
scttcper wants to merge 5 commits into
masterfrom
scttcper/resolved-release-pr-link
Draft

feat(issues): Link commit activities to pull requests#119373
scttcper wants to merge 5 commits into
masterfrom
scttcper/resolved-release-pr-link

Conversation

@scttcper

@scttcper scttcper commented Jul 9, 2026

Copy link
Copy Markdown
Member

Commit-backed issue activities already have pull request data, but the new issue activity feed mostly stops at the release or commit.

Behind issue-activity-feed-v2, this prefers the pull request for resolved-in-release activities and adds the pull request alongside referenced commits. The legacy activity feed is unchanged.

Depends on #119372. Screenshots will follow once the dependent API payload is available in a runnable environment.

Resolved-in-release activities only linked to the release even when Sentry knew which commit caused the resolution.

Prefer the associated pull request in both activity feeds and fall back to the exact commit when there is no PR. Activities without the new backend data keep the existing display.

Co-Authored-By: GPT-5 <noreply@openai.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 9, 2026
Referenced commit activities already include the associated pull request, but the activity feed only showed the commit.

Keep the commit context and add the pull request link when it is available in both activity feed variants.

Co-Authored-By: GPT-5 <noreply@openai.com>
@scttcper scttcper changed the title feat(issues): Link release resolutions to pull requests feat(issues): Link commit activities to pull requests Jul 9, 2026
Keep the pull request links limited to the new issue activity feed behind issue-activity-feed-v2. Restore the legacy renderer and remove its new test coverage.

Co-Authored-By: GPT-5 <noreply@openai.com>
scttcper and others added 2 commits July 10, 2026 09:12
The semver and non-semver suffixes add noise next to the release link in the new activity feed. Keep the release context and drop the classification text.

Co-Authored-By: GPT-5 <noreply@openai.com>
Keep the activity tests focused on the links we render instead of asserting removed text stays absent.

Co-Authored-By: GPT-5 <noreply@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant