Repository navigation
ci: update sdk_release's driver/mxdriver pointer directly on main push - #25
Merged
Merged
Conversation
mxdriver_dev's sync_to_public.yml pushes straight to this repo's main (not via a reviewed PR), so the existing notify_parent.yml (pull_request: closed only) never fires for that path. sdk_release's driver/mxdriver pointer therefore only moved via the daily bulk sync_main.yml cron, which silently failed for two days in a row (2026-10-05/06) when it landed on a broken ci-sync-runner_7. Mirror the direct-update pattern other sdk_release children already use (mu_debugger, pxl, xif, xpti, xprofiler's parent_module_update.yml) so every push to main here updates sdk_release's main immediately, on its own runner pool, independent of the bulk cron.
jaehyuk-XCENA
force-pushed
the
jaehyuk/ci/direct-update-sdk-release-on-push
branch
from
October 8, 2026 04:13
951a32e to
b754b47
Compare
4 tasks
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
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.
📌 목적
mxdriver_dev→mxdriver(public) main 동기화가 PR 없이 직접 push 되는 경로라, 기존notify_parent.yml(pull_request: closed전용)이 반응하지 못해sdk_release의driver/mxdriver포인터가 레거시 벌크 cron(sync_main.yml) 하나에만 의존하고 있었다. 그 cron이 조용히 실패하면 포인터가 며칠씩 밀린다.📝 상세 내용
문제 / 근본 원인
mxdriver_dev의sync_to_public.yml은 리뷰 PR 없이 main에 바로git push한다.notify_parent.yml은pull_request: closed에서만 fire 하므로 그 직접 push를 못 잡는다.driver/mxdriver포인터는 sdk_release의 일일 벌크 cron(sync_main.yml→.github의sync-submodules.yml) 단 하나의 경로에만 의존했다.ci-sync-runner_7)의 PATH/sudo 문제로 "Set Git user" 스텝에서부터 조용히 실패해, mxdriver의 포인터가 그 사이 올라온 upstream 커밋들을 못 따라가다 수동으로 맞춰야 했다.변경
.github/workflows/parent_module_update.yml추가 — sdk_release의 다른 자식들(mu_debugger,pxl,xif,xpti,xprofiler)이 이미 쓰는 패턴 그대로, main push 시xcena-dev/.github의submodule-update.yml을 호출해 sdk_release main의driver/mxdriver포인터를 즉시 직접 commit+push 한다.notify_parent.yml은 그대로 둔다(건드리지 않음).sync_main.yml)도 백업으로 그대로 유지한다.검증
xcena-dev/sdk_release의.gitmodules에서driver/mxdriver경로 확인(git@github.com:xcena-dev/mxdriver.git, pathdriver/mxdriver).mu_debugger/sdk_release자신의parent_module_update.yml과 구조 동일함을 대조 확인(gh api .../contents/.github/workflows/parent_module_update.yml).남은 것 / 리스크
update-submodule-runner풀에서 실제로 성공하는지는 머지 후 다음 push에서 확인 필요.METISX_GIT_ACTION_ACCESS_TOKENsecret이 이 repo(public)에도 유효 범위로 등록돼 있는지 org 시크릿 조회 권한이 없어 직접 확인은 못 함 — 실패 시 1순위 확인 대상.cli/mu_lib(→sdk_release) /mxperfsim_release세 repo도 같은 구조적 공백이 있음 — 이 PR 범위 밖, 별도 조치 필요.🔗 관련 이슈(선택)
✅ 검증 기준 (Acceptance Criteria)
🌿 관련 PR(선택)
없음
🌿 상위 Repo(선택)
없음
🌿 관련 Branch(선택)
📦 Release Note (자동 생성용 / 영문 작성)
NEW
CHANGED
FIXED
IMPORTANT NOTES