sync: bring main ancestry into develop for protected promotion - #3058
Merged
Merged
Conversation
promote: 타입 수정이 포함된 develop을 data로 올린다
promote: 타입 수정이 포함된 data를 main으로 올린다
|
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.
dataandmainhave the same tree but are one and two promotion commits ahead ofdevelop. Protecteddatarequires its PR head to include the current base ancestry. Merge currentmainintodevelopthrough this temporary feature branch so #3057 can advance without bypassing branch protection.The merge commit has parents
91ee69c7(develop) and25530935(main). Its Git tree is exactly the currentdeveloptree (2de4984f), so this PR changes ancestry only and adds no source or artifact bytes. After this merge, continue #3057 (develop → data) and thendata → main.