Skip to content

sync-upstream.sh: refuse a stale script copy; fix the header's run location #61

Open

Description

@ziyadakl

Problem

On 2026-11-03 the update ran sync-upstream.sh check from the fork checkout ~/dev/2-personal/t3code/t3code, which sat on an old custom-v2 with the old script. That old check ran the tests for 11 minutes before it was stopped. The script's own header still points there: scripts/custom/sync-upstream.sh:3 says "Run on affinity-vps from the fork checkout."

Change

  • check (and footprint) refuse to run when the script file itself differs from origin/custom-v2:scripts/custom/sync-upstream.sh, and print the git pull --ff-only to run.
  • Fix the header line 3: run start from the fork checkout after git pull --ff-only, and check from wt-sync.

Done when

Running the old script copy against a newer origin/custom-v2 stops in under a second with the pull command.

Source: retro of the T3 updates, routine in the t3-update skill (step 1).

Activity

  1. ziyadakl commented on Nov 6, 2026

    @ziyadakl
    OwnerAuthor

    Also from the 2026-11-06 sync: check refused to start in the VPS shell, which has Node 22 and no fnm. A helper had to find Node 26 by hand at ~/.local/share/fnm/node-versions/v26.12.1/installation/bin. The script should put the newest installed Node 26 on PATH itself, or print that exact export line when it refuses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions