From b754b47944e59491e3f59c5f2918c1537f8c82be Mon Sep 17 00:00:00 2001 From: jaehyuk park Date: Thu, 8 Oct 2026 13:10:34 +0900 Subject: [PATCH] ci: update sdk_release's driver/mxdriver submodule directly on main push 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. --- .github/workflows/parent_module_update.yml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 .github/workflows/parent_module_update.yml diff --git a/.github/workflows/parent_module_update.yml b/.github/workflows/parent_module_update.yml new file mode 100644 index 0000000..4b56d1b --- /dev/null +++ b/.github/workflows/parent_module_update.yml @@ -0,0 +1,17 @@ +name: Update Parent Repository on Push + +on: + push: + branches: + - main + +jobs: + update-parent: + uses: xcena-dev/.github/.github/workflows/submodule-update.yml@main + with: + parent_repository: 'xcena-dev/sdk_release' + checkout_branch: 'main' + submodule_path: 'driver/mxdriver' + submodule_branch: 'main' + secrets: + PAT_TOKEN: ${{ secrets.METISX_GIT_ACTION_ACCESS_TOKEN }}