Repository navigation
Reconcile data promotion history without changing source bytes - #3204
Merged
Merged
Conversation
Promote shared SDK recovery and held review-media tooling to data
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Strict data promotion requires the prior protected data merge to be an ancestor of develop. The normal #3199 data merge d608d9f was not in develop, so #3203 reports BEHIND despite the reviewed source changes.
This branch merges that exact existing data history into the current develop candidate through a normal codex → develop PR. No source or evidence bytes change. Before/after Git tree equality is verified: c6fb5c706b9847234e4fa0781364ee4d314fc724. No protected ref was directly updated and no force push is used.
Existing #3202 source validation remains applicable to the identical tree. Required current-head CI and conversation resolution still apply. This PR does not claim deployment, hosted SQL, memory improvement, or field results.