chore(sync): reconcile the e2a253ec, d4f2ca02 and a7f26a32 entries with #455 - #456
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
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.
Linked issue
Bookkeeping for #455.
Type of change
Description
The three ledger entries added by #455 were written with
pr: "pending-merge"/b24ui_sha: "pending-merge", because the PR carrying them had not merged yet. They now point at #455 and its squash SHA3b1b017e..sync/PORTING.md§6 step 4 has the next port reconcile the previous entry; the last entry of a run has no follower, so it gets its own small PR. Here the whole run was one batch of three, so all three are closed out together. No entry in the ledger is left unreconciled.Bookkeeping only — no source, test or docs change.
Checklist
Generated by Claude Code