feat: baseline PR trend line against the base branch#195
Merged
Conversation
On pull_request builds, the trend line and CI-summary/HTML trend blocks now baseline against the compare branch's latest run instead of the current branch's own rolling history, and label the baseline (e.g. `vs main`) so it is unambiguous. All three metrics share one consistent baseline. Add a `compare-branch` input (defaults to the PR base branch) and skip self-compares.
Contributor
Contributor
🔬 TestGlance✅ 758 passed across 1 job — 100.0% · ⏱️ 2.4s
🟡 test — details✅ 758 passed
vs
Updated 2026-07-07T20:01:01.889Z |
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.
Summary
On
pull_requestbuilds, the trend line and the CI-summary/HTML trend blocks now baseline against the compare branch's latest run (default: the PR base branch) instead of the current branch's own rolling history, with all three metrics sharing one consistent baseline. The baseline is labeled in the output (e.g.vs `main`) so it is no longer ambiguous, and a newcompare-branchinput lets you override which branch to compare against. It falls back to current-branch trends when the compare branch has no history and skips self-compares; docs (README,action.yml,.agents/) are updated to match.Test plan
pnpm typecheck,pnpm lint,pnpm format:check, andpnpm buildall green (dist/left to CI)