Repository navigation
ci: also run Bencher perf tests on fork PRs - #1619
Merged
Merged
Conversation
jkaczman
added this pull request to stack #1620
September 23, 2026 12:30
jkaczman
force-pushed
the
jk-bencher-2-step-forks
branch
from
September 23, 2026 22:46
128829a to
5ed1e0a
Compare
jkaczman
force-pushed
the
jk-bencher-2-step-forks
branch
from
September 28, 2026 13:38
4506685 to
18240e6
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
jkaczman
force-pushed
the
jk-bencher-2-step-forks
branch
from
September 28, 2026 17:32
18240e6 to
029d48d
Compare
jkaczman
force-pushed
the
jk-bencher-2-step-forks
branch
from
September 28, 2026 21:44
9acb829 to
1866550
Compare
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
1 participant
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.
In addition to #1617, also run perf regression tests on fork PRs.
This uses Bencher's recommended 2-step PR workflow (with some minor tweaks) to safely make sure that forks can't abuse
GITHUB_TOKEN/BENCHER_API_KEY/ etc.Steps: