Runner: --include-prs records the PRs since the previous result set - #78
Merged
NullVoxPopuli merged 1 commit intoJul 29, 2026
Conversation
The latest result set's notes.prs was hand-collected. With --include-prs the runner records it instead: result files are named with the run's ISO timestamp, so the previous result set's date is the newest other filename, and the PRs that landed since come from git history alone (no GitHub API) -- merge commits carry the number in the subject and the title in the body, squash merges carry both in the subject. The list is printed before the 'does this look correct?' confirm, and merged into notes.prs deduplicated by URL, so hand-added entries (plain URL strings) and earlier appends survive. The results app shows the list in a <details> under the run info: 'NullVoxPopuli#76 <title>' for runner entries, 'NullVoxPopuli#72' for hand-added strings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@NullVoxPopuli-ai-agent is attempting to deploy a commit to the NullVoxPopuli's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
The latest result set's
notes.prswas collected by hand (6086a0c). This adds--include-prsso the runner records it instead — from git history alone, no GitHub API.How it works
"When was the last result set?" Result files are named with the run's ISO timestamp, so the previous set's date is simply the newest filename in
results/public/results/other than the file being written — which also does the right thing when appending to today's file (the previous set becomes the one before it)."Which PRs landed since?"
git log --since=<that date>, matching both merge shapes:Merge pull request #N from ...in the subject, PR title as the first body lineThe PR title (#N)in the subjectDeduplicated by number, newest first.
The list is printed before the "does this information look correct?" confirm, so what will be recorded is part of the pre-run review.
Saved as
notes.prsentries of{ url, title }, merged with whatever is already there and deduplicated by URL — hand-added entries (plain URL strings, like the existing file) and earlier appends survive.Results app
The run-info block (
<Info />) now shows the list in a<details>:Runner-recorded entries render as
#76 — <title>; hand-added string entries render as just#72(both link to the PR). The existing 2026-07-29 result set's hand-added notes render as-is, verified in the dev server at 1920px along with the titled shape.Verified
prs.tsrun against real history: pretending a new file exists yields PRs Tests: opt-in conformance suite — detect benchmark cheating via DOM update traces #76/feat(react) bench maxing react by using useLayoutEffect #74/Rework variant display and add experiment support in History view #75/feat(bench): set up mac support #73 with correct titles; pretending to append to the 2026-07-29 file yields 9 PRs since the 07-26 set.savePrNoteson a copy of the real 2026-07-29 file: the three hand-added strings stay, a duplicate of Vue vapor #72 is skipped, Tests: opt-in conformance suite — detect benchmark cheating via DOM update traces #76 appends, and thevue: { variant: "Vapor" }note is untouched.ember-tsc --noEmit, eslint (root + results), and prettier all pass.🤖 Generated with Claude Code