Skip to content

Make experimental VS insertion reviewers configurable - #14632

Merged
ViktorHofer merged 2 commits into
mainfrom
exp/raines/exp-insertion-reviewers
Aug 4, 2026
Merged

Make experimental VS insertion reviewers configurable#14632
ViktorHofer merged 2 commits into
mainfrom
exp/raines/exp-insertion-reviewers

Conversation

@rainersigwald

@rainersigwald rainersigwald commented Aug 3, 2026

Copy link
Copy Markdown
Member

Every experimental VS insertion assigned MSBuild as the reviewer, so the entire team got pinged for one person's one-off experiment. Experimental insertions should be reviewed by whoever owns the experiment.

Approach

Reviewers now resolve in this order:

  1. A new free-form InsertionReviewers pipeline parameter, so reviewers can be chosen at insertion-job-schedule time.
  2. Otherwise, the alias is parsed out of the branch name using the exp/{alias}/{branchname} convention.
  3. Otherwise, no reviewers at all, plus a warning log issue explaining that the branch does not follow the convention.

Only vs-insertion-experimental.yml changes. The production vs-insertion.yml keeps MSBuild,VS ProTools.

Notes for reviewers

  • The parameter reaches the script through an env: block rather than inline ${{ }}. Inline expansion is textual substitution into the PowerShell source, and this parameter is free-form user input.

Experimental insertions hardcoded `MSBuild` as the reviewer, which pinged
the whole team for one person's experiment.

Reviewers now resolve as: the new queue-time `InsertionReviewers`
parameter, else the alias from the `exp/{alias}/{branchname}` branch
convention, else none (with a warning).

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d609599e-76bb-479a-85d4-e59df4f373a6
@rainersigwald

Copy link
Copy Markdown
Member Author

Pushed this to two branches and got https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/765624 (with normal format, correctly assigned to me) and https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/765623 (showing the fallback to no-reviewer-specified works).

@rainersigwald
rainersigwald marked this pull request as ready for review August 3, 2026 20:09
Copilot AI review requested due to automatic review settings August 3, 2026 20:09

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the experimental VS insertion pipeline so reviewers are no longer hardcoded to the MSBuild team, reducing unnecessary review notifications by allowing per-experiment ownership to drive reviewer assignment.

Changes:

  • Adds a new free-form InsertionReviewers queue-time pipeline parameter.
  • Resolves reviewers via parameter first, then by parsing the exp/{alias}/{branchname} branch convention, otherwise assigns none and logs a warning.
  • Routes the resolved value into MicroBuildInsertVsPayload via a runtime variable (FinalInsertionReviewers).

Comment thread azure-pipelines/vs-insertion-experimental.yml Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@ViktorHofer
ViktorHofer merged commit 7905b8a into main Aug 4, 2026
12 checks passed
@ViktorHofer
ViktorHofer deleted the exp/raines/exp-insertion-reviewers branch August 4, 2026 06:27
@JanProvaznik

Copy link
Copy Markdown
Member

I kind of don't like this because now when you create an experimental insertion it's super easy to forget about it and you can't see it in the default view https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequests?_a=mine

@rainersigwald

Copy link
Copy Markdown
Member Author

If you have your alias in the branch it should be:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants