Repository navigation
chore(upstream): advance intake baseline to 3997b9a3a4 - #517
Merged
Merged
Conversation
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.
The upstream intake queue's baseline was still at
2a30353530, though main has since taken every upstream commit through3997b9a3a4(the pingdotgg#10915 squash merge). Batch 17 was promoted asfcdebff60c. This moves the baseline to that boundary, so the next batch starts at pingdotgg#10660.It also removes five entries from
.github/upstream-tracked-prs.jsonthat the batch recorded: pingdotgg#10839, pingdotgg#10870, pingdotgg#10875, pingdotgg#10983 and pingdotgg#11002. Their follow-ups stay tracked.This PR changes only those two state files; it contains no intake commits.
Validation
node scripts/upstream-queue.ts advance 3997b9a3a4ee6b43ee768a9b372ff3dd52fd840eaccepted the boundary. The command rejects a boundary with unresolved earlier commits or one inside a multi-commit PR.node scripts/upstream-queue.ts statusafterwards: baseline and reconciled-through are both3997b9a3a4; 382 of 403 commits up to the target are pending, 21 recorded, no exceptions. No tracked PR is listed as recorded.node scripts/upstream-queue.ts next --count 1now starts at fix(web): save PR body edits with Cmd/Ctrl+Enter pingdotgg/t3code#10660.Written by an agent (Claude Code, claude-opus-5-5).