Skip to content

perf: benchmarks gh-pages publish workflow (#164) — protected-only PR#243

Merged
Chris-Wolfgang merged 2 commits into
mainfrom
protected/abs-benchmarks-workflow
Jun 24, 2026
Merged

perf: benchmarks gh-pages publish workflow (#164) — protected-only PR#243
Chris-Wolfgang merged 2 commits into
mainfrom
protected/abs-benchmarks-workflow

Conversation

@Chris-Wolfgang

Copy link
Copy Markdown
Owner

Adds .github/workflows/benchmarks.yaml — the BenchmarkDotNet → gh-pages chart publisher. Closes #164.

Protected-only PR (the workflow is the only protected file) split from the benchmark-project PR #242 so the project lands through normal review and only this one file needs the bypass.

What it does

On push to main touching src/** or benchmarks/**, runs the benchmarks (--job short) and publishes the result to gh-pages under dev/bench/ via benchmark-action/github-action-benchmark (SHA-pinned). Decoupled from PR/release — it's a tracker, not a gate (fail-on-alert: false).

Expected CI

  • Detect .NET Projects ❌ — expected; admin-bypass merge.
  • Stage 1/2/3 SKIPPED (depend on the guard).

Depends on #242 (the benchmark project) being merged first so the workflow's project path exists. The canonical docfx.yaml already preserves dev/ on gh-pages.

Follows: #242

…y PR

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

[Maintenance] performance: Publish benchmark-result graphs to gh-pages

1 participant