Repository navigation
ci(bench): name the branch in every regression issue - #566
Merged
Merged
Conversation
Issues for main were titled "Benchmark regression: <suite>" with no branch, while v3 issues carried "(v3)". Title every issue "Benchmark regression: <suite> (<branch>)", like the nightly fuzz issue, and add a Branch line to the body. An open issue with the old main title is still matched, renamed and commented on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HyLscCUuJ1GQpdAeX79EdR
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nightly benchmark regression issues for
mainwere titledBenchmark regression: <suite>with no branch (only v3 got(v3)), so an issue like #562 didn't say which branch regressed.Benchmark regression: <suite> (<branch>), matchingNightly fuzz failure (<branch>).**Branch:**line; label is<suite>, <branch>for every branch).Targets
mainbecause scheduled runs always use the default branch'sbench.yml; it reachesv3with the next main → v3 merge.Checked: YAML parses, embedded script passes
node --check.🤖 Generated with Claude Code
https://claude.ai/code/session_01HyLscCUuJ1GQpdAeX79EdR