You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Release plan]: Improve and unify the SDK PR review dashboard across languages #17149
Different language teams currently use different ways to track SDK PR review status. The goal is to bring these experiences together in the Azure SDK Release Plan Dashboard and provide a common SDK PR review view across languages.
The current SDK PR view provides a starting point, but it needs further improvement to better support our daily PR review work. This issue will track feedback and proposals around:
What information reviewers need to quickly understand SDK PR status and identify PRs requiring attention.
What review actions should be available from the dashboard.
How the layout can make pending work, issues, and next steps easier to understand.
What useful capabilities from existing language-specific solutions, such as daily notifications or separate dashboards, should be incorporated.
How to provide a consistent experience across languages while still supporting language-specific needs.
Wondering whether it is worthwhile to make the dashboard agent friendly. E.g. it is very easy for agent to "list all open AutoPR from Java SDK repo" and "check if any of them has HEAD updated" -- so that agent would focus on these for review (skip PR already reviewed) -- we have a local agent to do things that an agentic workflow cannot do or not safe to do.
For dashboard, agent would need to use devop API to access release plan items, then handle schema there. This is less well-known than GitHub APIs.
<-- the question is whether this is worthwhile. Or checking GitHub is already good enough for SDK reviewers/agents.
I am curious why we want to integrate the 'SDK PR review View' to the release plan dashboard. Per my understanding, they are used for different people. Will service team be able to access the SDK PR review panel as well?
This is the dashboard that JS is currently using: https://ca-sdk-js-worker.ambitiouspond-79d04e69.eastus2.azurecontainerapps.io/#/sdk-prs (need to sign in with aad account). I plan to add more JS language related capabilities, but for now it's used for JS SDK PR reviews only. What matters most to me is: “Are there any new activities that need to be checked?”
7. I am curious why we want to integrate the 'SDK PR review View' to the release plan dashboard. Per my understanding, they are used for different people. Will service team be able to access the SDK PR review panel as well?
This is the dashboard that JS is currently using: https://ca-sdk-js-worker.ambitiouspond-79d04e69.eastus2.azurecontainerapps.io/#/sdk-prs (need to sign in with aad account). I plan to add more JS language related capabilities, but for now it's used for JS SDK PR reviews only. What matters most to me is: “Are there any new activities that need to be checked?”
No, this view is for SDK release owners and CAT team only. I don't expect service team to access or use this view though they probably still have the permission to access it.
I believe most of the thing different SDK reviewers care about should be similar across different languages. So moving forward, we don't want each team to maintain their own view but have a unified one across different languages.
Activity
lirenhe commentedon Sep 30, 2026
cc Laurent Mazuel (@lmazuel) Praveen Kuttappan (@praveenkuttappan) for awareness. We are also collecting what people expect for this dashboard.
weidongxu-microsoft commentedon Oct 9, 2026
Wondering whether it is worthwhile to make the dashboard agent friendly. E.g. it is very easy for agent to "list all open AutoPR from Java SDK repo" and "check if any of them has HEAD updated" -- so that agent would focus on these for review (skip PR already reviewed) -- we have a local agent to do things that an agentic workflow cannot do or not safe to do.
For dashboard, agent would need to use devop API to access release plan items, then handle schema there. This is less well-known than GitHub APIs.
<-- the question is whether this is worthwhile. Or checking GitHub is already good enough for SDK reviewers/agents.
JialinHuang803 commentedon Oct 9, 2026
I am curious why we want to integrate the 'SDK PR review View' to the release plan dashboard. Per my understanding, they are used for different people. Will service team be able to access the SDK PR review panel as well?
This is the dashboard that JS is currently using: https://ca-sdk-js-worker.ambitiouspond-79d04e69.eastus2.azurecontainerapps.io/#/sdk-prs (need to sign in with aad account). I plan to add more JS language related capabilities, but for now it's used for JS SDK PR reviews only. What matters most to me is: “Are there any new activities that need to be checked?”
lirenhe commentedon Oct 15, 2026
No, this view is for SDK release owners and CAT team only. I don't expect service team to access or use this view though they probably still have the permission to access it.
I believe most of the thing different SDK reviewers care about should be similar across different languages. So moving forward, we don't want each team to maintain their own view but have a unified one across different languages.
lirenhe commentedon Oct 15, 2026
Set the SH priority to high as it is added into our commitment.
lirenhe commentedon Nov 11, 2026
Jialin Huang (@JialinHuang803), I assign this to you, as we need a updated view in Release planner for this effort, please work with Praveen Kuttappan (@praveenkuttappan) with more details. thanks