Skip VMR user change validation for dotnet-bot PRs by Copilot · Pull Request #4538 · dotnet/dotnet

Copilot · 2026-01-29T21:58:42Z

The ValidateUserChanges pipeline stage was blocking automated PRs from dotnet-bot, treating them as user changes requiring validation.

Changes

Added Build.RequestedFor check to exclude dotnet-bot from the ValidateUserChanges stage condition in eng/pipelines/pr.yml

condition: and(
    eq(variables['isPRTrigger'], 'true'),
    and(
        not(startsWith(variables['System.PullRequest.SourceBranch'], 'refs/heads/darc-')),
        not(startsWith(variables['System.PullRequest.SourceBranch'], 'darc-')),
        not(eq(variables['Build.RequestedFor'], 'dotnet-bot'))
    )
)

This follows the existing pattern where DARC branches skip validation, extending it to all dotnet-bot automated changes.

Original prompt

This section details on the original issue you should resolve

<issue_title>Update VMR Run Validation Script to allow changes from dotnet-bot</issue_title>
<issue_description>See #4515

The "Validate user changes in VMR Run Validation Script" job currently does not allow changes from the dotnet-bot account. This update is needed to accept and validate changes pushed or submitted by dotnet-bot, so automation and bot-driven infrastructure can run as expected.</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes Update VMR Run Validation Script to allow changes from dotnet-bot #4537

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: ellahathaway <67609881+ellahathaway@users.noreply.github.com>

Copilot

Pull request overview

This PR modifies the ValidateUserChanges pipeline stage to skip validation for pull requests created by dotnet-bot, preventing automated PRs from being incorrectly blocked as user changes requiring validation.

Changes:

Added Build.RequestedFor check to exclude dotnet-bot from ValidateUserChanges stage validation in the PR pipeline
Follows the existing pattern of skipping validation for DARC automated branches

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-30T17:45:10Z

eng/pipelines/pr.yml

                  not(startsWith(variables['System.PullRequest.SourceBranch'], 'refs/heads/darc-')),
-                  not(startsWith(variables['System.PullRequest.SourceBranch'], 'darc-'))
+                  not(startsWith(variables['System.PullRequest.SourceBranch'], 'darc-')),
+                  not(eq(variables['Build.RequestedFor'], 'dotnet-bot'))


Consider adding a pipeline run with logging to verify that Build.RequestedFor equals exactly "dotnet-bot" for bot-created PRs. Azure Pipelines populates this variable with the GitHub user's display name, which should be "dotnet-bot" for the bot account, but it's worth confirming. If this check doesn't work as expected, alternative options include: checking Build.RequestedForEmail (e.g., ends with @users.noreply.github.com), or combining this with additional branch name patterns that dotnet-bot uses.

ellahathaway · 2026-01-30T21:07:20Z

/backport to release/10.0.1xx

github-actions · 2026-01-30T21:07:29Z

Started backporting to release/10.0.1xx (link to workflow run)

github-actions · 2026-01-30T21:09:33Z

@ellahathaway backporting to release/10.0.1xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

ellahathaway · 2026-02-04T15:40:03Z

/backport to release/10.0.1xx

ellahathaway · 2026-02-04T15:40:13Z

/backport to release/10.0.2xx

github-actions · 2026-02-04T15:40:15Z

Started backporting to release/10.0.1xx (link to workflow run)

ellahathaway · 2026-02-04T15:40:20Z

/backport to release/10.0.3xx

github-actions · 2026-02-04T15:40:24Z

Started backporting to release/10.0.2xx (link to workflow run)

github-actions · 2026-02-04T15:40:31Z

Started backporting to release/10.0.3xx (link to workflow run)

github-actions · 2026-02-04T15:42:25Z

@ellahathaway backporting to release/10.0.1xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Creating an empty commit: Initial plan
Applying: Update ValidateUserChanges stage to skip dotnet-bot PRs
Using index info to reconstruct a base tree...
M	eng/pipelines/pr.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/pr.yml
CONFLICT (content): Merge conflict in eng/pipelines/pr.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Update ValidateUserChanges stage to skip dotnet-bot PRs
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

github-actions · 2026-02-04T15:42:40Z

@ellahathaway backporting to release/10.0.3xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Creating an empty commit: Initial plan
Applying: Update ValidateUserChanges stage to skip dotnet-bot PRs
Using index info to reconstruct a base tree...
M	eng/pipelines/pr.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/pr.yml
CONFLICT (content): Merge conflict in eng/pipelines/pr.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Update ValidateUserChanges stage to skip dotnet-bot PRs
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

github-actions · 2026-02-04T15:42:42Z

@ellahathaway backporting to release/10.0.2xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Creating an empty commit: Initial plan
Applying: Update ValidateUserChanges stage to skip dotnet-bot PRs
Using index info to reconstruct a base tree...
M	eng/pipelines/pr.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/pr.yml
CONFLICT (content): Merge conflict in eng/pipelines/pr.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0002 Update ValidateUserChanges stage to skip dotnet-bot PRs
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

Initial plan

a8df7d1

Copilot AI assigned Copilot and ellahathaway Jan 29, 2026

Copilot started work on behalf of ellahathaway January 29, 2026 21:59 View session

Update ValidateUserChanges stage to skip dotnet-bot PRs

77009f5

Co-authored-by: ellahathaway <67609881+ellahathaway@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Update VMR Run Validation Script to accept dotnet-bot changes~~ Skip VMR user change validation for dotnet-bot PRs Jan 29, 2026

Copilot AI requested a review from ellahathaway January 29, 2026 22:26

Copilot finished work on behalf of ellahathaway January 29, 2026 22:26

ellahathaway marked this pull request as ready for review January 30, 2026 17:39

ellahathaway requested review from a team as code owners January 30, 2026 17:39

ellahathaway requested review from ViktorHofer and Copilot January 30, 2026 17:39

Copilot started reviewing on behalf of ellahathaway January 30, 2026 17:41 View session

mmitche approved these changes Jan 30, 2026

View reviewed changes

Copilot AI reviewed Jan 30, 2026

View reviewed changes

ellahathaway merged commit ed34c37 into main Jan 30, 2026
17 checks passed

ellahathaway deleted the copilot/update-vmr-validation-script branch January 30, 2026 21:07

ellahathaway mentioned this pull request Feb 11, 2026

.NET 10.0.103 February 2026 Updates #4770

Merged

Conversation

Copilot AI commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Comments on the Issue (you are @copilot in this section)

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

ellahathaway commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

ellahathaway commented Feb 4, 2026

Uh oh!

ellahathaway commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

ellahathaway commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Copilot AI commented Jan 29, 2026 •

edited

Loading