From 7e7ef73a8c174066e0c391f9d9f41f04ad8ea6e8 Mon Sep 17 00:00:00 2001 From: vasilito Date: Sun, 19 Jul 2026 05:38:30 +0900 Subject: [PATCH] upgrade-forks: fix relative fork_dir after cd into fork (cd-back bug) The script cd's into the fork dir for the clean-tree check (line ~202) and never returns to PROJECT_ROOT. Every subsequent relative 'cd "$fork_dir"' subshell then fails with 'No such file or directory', making single-fork and multi-fork runs always FAIL at the upstream-ref resolution step. Make fork_dir absolute at assignment so all subshell cd/git calls work regardless of current directory. Found while attempting the base fork sync (verify-fork-functions gate). --- local/scripts/upgrade-forks.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/local/scripts/upgrade-forks.sh b/local/scripts/upgrade-forks.sh index 68207058ac..637297a5c6 100755 --- a/local/scripts/upgrade-forks.sh +++ b/local/scripts/upgrade-forks.sh @@ -146,7 +146,7 @@ declare -a FAILED_FORKS=() declare -a SUCCEEDED_FORKS=() for fork in "${TARGET_FORKS[@]}"; do - fork_dir="local/sources/${fork}" + fork_dir="$PROJECT_ROOT/local/sources/${fork}" echo -e "${BLUE}=== ${fork} ===${NC}"