chore(repo): main/data를 develop으로 동기화 - #2996
Merged
Merged
Conversation
chore(repo): develop을 data로 승격
chore(repo): data를 main으로 승격
…into-develop-20260922k
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
무엇을 하나
develop이main/data보다 뒤처지지 않도록 두 브랜치를develop으로 합칩니다. 보호 브랜치 승격(develop -> data -> main)이 base 최신 상태를 요구하기 때문에 필요한 단계입니다.origin/main병합:e3ddea24(chore(repo): data를 main으로 승격 #2993),bc4f3368(chore(repo): develop을 data로 승격 #2992) — 트리 변화 없는 승격 병합 커밋origin/data병합: 이미 최신확인
git diff origin/develop HEAD결과 없음 (내용 변화 없는 병합)