Skip to content

Add PR-supplied EgorBot vetting to microbenchmark skill - #136076

Open
eiriktsarpalis wants to merge 1 commit into
mainfrom
eiriktsarpalis-pr-performance-vetting
Open

eiriktsarpalis wants to merge 1 commit into
mainfrom
eiriktsarpalis-pr-performance-vetting

Conversation

@eiriktsarpalis

Copy link
Copy Markdown
Member

The existing microbenchmark workflow starts with custom benchmarks and local builds. Add a dedicated route for vetting an explicitly supplied PR URL through EgorBot, reusing canonical dotnet/performance benchmarks before considering custom code.

  • Inspect changed paths and justify benchmark coverage; custom snippets only fill demonstrated coverage gaps.
  • Deduplicate requests against the inspected PR head, allowing fresh requests after new commits. Use separate canonical and custom invocation comments when mixed coverage requires both.
  • Stop after posting the invocation comments, without local builds, benchmark execution, or result polling.

The route supports open dotnet/runtime PRs targeting main and uses EgorBot's default current-main-versus-merged-PR comparison. Existing skill metadata, local-only measurements, and legacy EgorBot behavior without a supplied PR URL are preserved.

Validation: Skill metadata and whitespace checks passed. Four fixture-driven dry-run scenarios passed all 24 assertions; the non-PR/local-only preservation control passed against both the original and updated skill. No live EgorBot jobs or benchmark comments were created during evaluation. No runtime builds or benchmarks were run for this skill-documentation change.

Note

This pull request description and the changes were generated with GitHub Copilot.

Add a canonical-first PR vetting route that dispatches focused EgorBot requests and stops after posting. Preserve existing metadata and local and legacy EgorBot workflows.

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

Copilot-Session: 9d231e5d-da7c-48a1-a069-50667b1ecc98
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
15 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@github-actions github-actions Bot added the area-skills Agent Skills label Oct 19, 2026

## Explicitly Supplied PR

When the user supplies a PR URL to vet its performance, use [PR-supplied EgorBot vetting](references/pr-vetting.md) instead of the local steps and legacy EgorBot guidance below, unless the user explicitly requests local-only measurements. That workflow selects benchmarks, posts the EgorBot invocation comment(s) on the supplied PR, and stops without waiting for results.

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.

This general skill and usage probably needs weigh-in from @EgorBo. It has the risk of automatically incurring a lot of additional overhead for something which is not a team owned, costed, or scaled utility.

This branch has not been deployed

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

Labels

area-skills Agent Skills

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants