Skip to content

Fix external PR reviewer assignment - #20303

Open
stephaniezyen wants to merge 2 commits into
mainfrom
fix-external-pr-review-assignment
Open

Fix external PR reviewer assignment#20303
stephaniezyen wants to merge 2 commits into
mainfrom
fix-external-pr-review-assignment

Conversation

@stephaniezyen

@stephaniezyen stephaniezyen commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace the Bicep External Maintainers team review request with explicit engineer usernames
  • avoid the 422 error caused by requesting review from a team that is not a repository collaborator

The listed engineers were taken from the current Bicep External Maintainers team membership and each has write access to the repository.

Follow-up to #19209.

Microsoft Reviewers: Open in CodeFlow

Replace the non-collaborator team review request with explicit reviewer usernames.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: fb00a3b8-0b0f-45e0-b788-8e1b53953043
@github-actions

github-actions Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Test this change out locally with the following install scripts (Action run 34631242476)

VSCode
  • Mac/Linux
    bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 34631242476
  • Windows
    iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 34631242476"
Azure CLI
  • Mac/Linux
    bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 34631242476
  • Windows
    iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 34631242476"

Comment thread .github/workflows/external-pr-review-assignment.yml Outdated
repo: context.repo.repo,
pull_number: context.payload.pull_request.number,
team_reviewers: ['bicep-external-maintainers']
reviewers: [

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can we not use a Github team here instead of naming people explicitly?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Jared is working on optimizing the Bicep repo's teams and removing any extraneous teams, so I don't know if it's helpful to keep and maintain a group just for this auto-assign bot, which is really what we're only using this group for.

The solution was to just specify each engineer in the auto-assign bot instead of maintaining a group and its permissions.

Happy to discuss with you and Jared though if you have reservations

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's have a discussion - this team doesn't need permissions to anything, and could potentially be a sub-team of an existing team. I don't think this would introduce a whole lot of admin overhead, and avoids separately tagging each username on every PR.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

See comments

Remove stephaniezyen and clarify the reviewer assignment step name.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: fb00a3b8-0b0f-45e0-b788-8e1b53953043
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.

2 participants