Repository navigation
chore(upstream): advance intake baseline to 014016a623 - #614
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
01e05c1526, though main has since taken every upstream commit through014016a623(the pingdotgg#11826 squash merge). The batch ending there was promoted as736c649758. This moves the baseline to that boundary, so the next batch starts at pingdotgg#11800.pingdotgg#11611 and pingdotgg#11813 leave the tracked upstream PR list. Both are recorded: the fork imported them early as
0ec137a760and13b75f6373.node scripts/upstream/queue.ts nexton this branch reports the baseline and reconciled boundary at014016a623, with no pending commits before pingdotgg#11800.Written by an agent (Claude Code, claude-opus-5-5).