[Improve] Show all linked pull requests in task surfaces - #1166
Draft
roomote-roomote[bot] wants to merge 2 commits into
Draft
[Improve] Show all linked pull requests in task surfaces#1166roomote-roomote[bot] wants to merge 2 commits into
roomote-roomote[bot] wants to merge 2 commits into
Conversation
Contributor
Contributor
Author
|
Addressed both unresolved Slack automation-footer comments in commit |
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
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.
What changed
Task workspace headers and Task Info now render every linked pull request with its canonical URL. Slack thread and automation footers now expose all active linked PRs instead of selecting one. Automation footer actions use unique IDs and stay within Slack's actions-block limit.
Why this change was made
Tasks can span multiple repositories and pull requests. Showing only the first or latest PR hid part of the work and made multi-PR tasks difficult to review.
Impact
Users can see and open the complete active PR set from the existing task surfaces, while compact task-list badges retain their existing behavior. Provider-specific PR URLs are preserved, and multi-PR automation footers remain valid Slack blocks.
Related PRs
Validation
Targeted web, communication, and Slack tests pass, including regression coverage for unique automation action IDs and the 24-PR cap. API, SDK, Slack, and web typechecks pass. Full visual proof remains unavailable because the proof runtime could not capture the seeded multi-PR state. The server-backed SDK router test also requires the unavailable
testdatabase.