Many devices, one remote

Git trail

GitHub is the source of truth. Laptops, a second PC, and a phone all push the same origin. Actions logs and git log are the ship record.

CONTRIBUTING.md in the repo is the short version. Do not force-push main. Do not commit .env.local or .data/.

The only happy path

  1. Branch feat/… or fix/… from main.
  2. PR. CI (typecheck, tests, lint, next build) must be green.
  3. Merge to main. Vercel Git Integration deploys production. Preview deploys exist on the PR.
  4. Optional: Actions → Deploy → Run workflow from GitHub mobile if VERCEL_TOKEN is set.

Phone

  • Site copy: /admin/phone → Site copy. Type PUBLISH. No git.
  • Merge / ship: GitHub mobile. Working Copy (iOS) or MGit (Android) if you must commit from the phone.
  • Listing photos: owner garage camera on the phone. That is product data, not git.
terminal
git checkout -b feat/short-name
git add -A
git commit -m "feat: what changed"
git push -u origin HEAD