Skip to content

Push benchmark results to gh-pages in a single push - #488

Merged
sinsoku merged 1 commit into
ruby:masterfrom
sinsoku:push-benchmark-results-once
Sep 26, 2026
Merged

sinsoku merged 1 commit into
ruby:masterfrom
sinsoku:push-benchmark-results-once

Conversation

@sinsoku

@sinsoku sinsoku commented Sep 26, 2026

Copy link
Copy Markdown
Collaborator

Motivation / Background

This Pull Request has been created because each Benchmark run pushes to gh-pages once per github-action-benchmark step, so GitHub Pages is deployed twice and the first deployment is always cancelled.

Detail

The second step now pushes both results at once. Since that step skips fetching gh-pages, it cannot recover from a push rejected by a concurrent run, so Benchmark runs share a concurrency group. As a result, a pending run is replaced when another commit lands on master, and some intermediate commits may have no benchmark result.

Verification

On my fork, a run with this change pushed to gh-pages once and deployed GitHub Pages once.

🤖 Generated with Claude Code

Each store step pushed to gh-pages, so GitHub Pages was deployed twice
per run and the first deployment was always cancelled.
@sinsoku
sinsoku merged commit 8448568 into ruby:master Sep 26, 2026
6 checks passed
@sinsoku
sinsoku deleted the push-benchmark-results-once branch September 26, 2026 02:56
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.

1 participant