submodule-bumplisted

# Bump a CUBRID submodule to a commit Dispatch `submodule-bump-receiver.yml` on `CUBRID/cubrid` so the parent repo pins a submodule to the commit you name. The Action opens a bump PR (or updates the open one). Normally the bump is automatic, one commit per PR; run this only when you need to catch up, pin a specific commit, or restart a stalled bump. **This triggers a real Action and touches a PR on the main repo.** Never dispatch without showing the user what will happen and getting a yes. ## Step 0: Check the state first (read-only) ```bash bash <skill-base-dir>/assets/bump_submodule.sh --status # all three, at a glance bash <skill-base-dir>/assets/bump_submodule.sh <submodule> --status # that one's pending commits ``` Read-only, so run it without asking first. One call reports, for all three submodules, the pinned SHA, the submodule head, how many commits are pending, and the open bump PR. **When the open PR already pins the head there is nothing to dispatch**: merging that PR is the whole job. The script says `just merge it` in that case, so guide the user to merge rather than suggesting a run. The per-submodule view lists only the commits added **after** the pinned one, oldest first and numbered (up to 20; beyond that it states how many remain). That number is exactly "how far to bump", so pick the SHA here when the user wants to stop at a specific commit. ## Step 1: Resolve the target | What the user says | workflow input `submodule_path` | submodule