Repo Transfer Checklist — sapience-design/arcive.io → <new-account>/arcive.io

Created: 2026-05-06 Purpose: End-to-end checklist for transferring the GitHub repo, with concrete file paths and commands. Run top to bottom.

Throughout this doc, replace <new-account> with the actual destination GitHub username (e.g. the account tied to sujith@arcive.io). Replace <old-account> with sapience-design.

---

Phase 0 — Pre-transfer (do these BEFORE clicking Transfer)

• Push every local branch so nothing exists only on a developer machine

  git push --all
  git push --tags

• Confirm no in-flight PRs (currently: master is clean, last merged PRs were #13 and #14 — ✅ clean window)
• Note the destination GitHub account is logged in somewhere so you can accept the transfer email
• Make sure Daniel’s GitHub username is known so you can re-invite him post-transfer
• List external integrations to repoint (use this doc — see Phase 3)

---

Phase 1 — Do the transfer

• On github.com/sapience-design/arcive.io → Settings → General → scroll to bottom → Danger Zone → Transfer ownership
• Type the destination username (the new personal account)
• Confirm the repo name to authorize
• Switch to the destination account, open the email, click Accept transfer
• Verify the repo now lives at https://github.com/<new-account>/arcive.io
• Verify old URL https://github.com/sapience-design/arcive.io redirects to the new path

---

Phase 2 — Re-add collaborators

Personal-account transfers do not carry collaborators. You must re-invite anyone who needs access.

• Go to https://github.com/<new-account>/arcive.io/settings/access
• Invite Daniel as a collaborator
• Invite partner (whichever account they use) as a collaborator
• Invite any other contributor

---

Phase 3 — Repoint external integrations

These services have a “GitHub repo” configured in their dashboard. The auto-redirect on github.com keeps webhooks working for now, but each one should be repointed to the new path for cleanliness and to avoid silent failure if/when the redirect ever expires.

Vercel (web app deploy)

• Go to Vercel dashboard → arcive project → Settings → Git
• Disconnect the sapience-design/arcive.io repo
• Reconnect to <new-account>/arcive.io
• Verify a manual redeploy succeeds

Supabase (cloud project)

• If the Supabase ↔ GitHub branch deploy integration is set up: dashboard → Project Settings → Integrations → re-link GitHub repo
• Verify the deploy hooks in the new repo’s webhooks list (Settings → Webhooks) point at *.supabase.co correctly

Modal (Python workers — transcribe, transcode, diarize, reid)

• If Modal has a GitHub deploy webhook: modal deploy doesn’t actually depend on the repo URL, so likely nothing to do
• Confirm by running modal deploy backend/modal/transcribe.py (or whichever entrypoint) succeeds from the new clone

Sentry

• Sentry dashboard → arcive project → Settings → Integrations → GitHub
• Update the linked repository to <new-account>/arcive.io
• Source maps + commit SHA linking will then point at the new path

Resend

• No repo linkage — domain auth is unrelated to GitHub. Skip.

Release Please (.github/workflows/release-please.yml)

• Workflow uses ${{ github.repository }} so it follows the repo automatically. Verify by checking the next release PR opens cleanly. Likely skip.

EAS / Expo (mobile)

• EAS doesn’t tie to GitHub repo for builds. Skip.

---

Phase 4 — Update in-repo references

These are the files in this repo that hardcode sapience-design. Search command:

git grep -n "sapience-design"

Should return only these (verified 2026-05-06):

File	Lines	Type
CHANGELOG.md	268–272	5 release-compare and tag URLs
docs/SHARING.md	13, 14, 15, 82	4 raw GitHub URLs
docs/03_PROGRESS.md	165	1 PR link (PR #6)
apps/web/app/(app)/about/page.tsx	3, 119	REPO_URL constant + display string
apps/web/app/(app)/talkback/page.tsx	43	1 ADR link

Update steps

• Run a global find/replace: sapience-design/arcive.io → <new-account>/arcive.io

  # PowerShell — preview matches first
  git grep -n "sapience-design"
  
  # Then edit each file (or use a script/IDE find-replace)

• Verify the about page renders with the new URL: npm run dev → http://localhost:3030/about
• Verify CHANGELOG.md release-compare links are clickable and resolve
• Commit: chore: repoint sapience-design → <new-account> after repo transfer

---

Phase 5 — Update local clones

Every developer with a local clone needs to repoint their origin remote.

Your machine

• Update the main clone:

  cd D:\Sapience\Projects\Arciv\2026
  git remote set-url origin https://github.com/<new-account>/arcive.io.git
  git remote -v   # verify
  git fetch       # verify connectivity

• If you have any worktrees or secondary clones, repeat for each

Daniel’s machine

• Send him this command:

  git remote set-url origin https://github.com/<new-account>/arcive.io.git
  git remote -v

Your partner’s machine

• Same command.

---

Phase 6 — Re-share collaboration links

Anything you sent under the old URL needs to be re-sent.

Prose.io link for the alignment doc (sent to your partner)

Old:

https://prose.io/#sapience-design/arcive.io/edit/master/docs/discussions/2026-05-06_cto_tasklist_alignment.md

New:

https://prose.io/#<new-account>/arcive.io/edit/master/docs/discussions/2026-05-06_cto_tasklist_alignment.md

• Re-send to your partner with the new URL

github.dev links (if any)

• Old: https://github.dev/sapience-design/arcive.io/... → new: https://github.dev/<new-account>/arcive.io/...

---

Phase 7 — Verification pass

After all of the above:

• Open a draft PR with a trivial change (e.g. typo fix in README) to confirm:
  • CI runs (.github/workflows/ci.yml)
  • Vercel preview deploys successfully
  • Supabase preview migration runs (if integration is set up)
  • PR creation works for collaborators (test by having Daniel push a branch)
• Run the e2e pipeline test to confirm Modal + Supabase still wire up:

  npm run test:e2e:cloud

• Click through the about page and confirm the GitHub link goes to the new repo
• Search the codebase one more time — git grep -n "sapience-design" should return zero matches
• Close the draft PR and delete the test branch

---

Phase 8 — Cleanup

• If the sapience-design GitHub account is no longer needed for ARCIVE work, you can leave it alone — old URLs will keep redirecting. No action required.
• If you want to revoke its access to other ARCIVE-adjacent integrations (Vercel team membership, etc.), do that in each service’s settings.
• Update this doc with anything you discovered during the transfer that future-you should know.

---

Rollback (if needed)

GitHub allows transferring back. If something goes catastrophically wrong:

• Destination account → Settings → Danger Zone → Transfer ownership → back to sapience-design
• Re-run Phases 3–6 in reverse

The repo data is never at risk. Only integration repointings need redoing.

---

Time estimate

Phase	Time
0 — Pre-transfer	5 min
1 — Transfer	5 min
2 — Re-add collaborators	5 min
3 — External integrations	15–20 min
4 — In-repo references (5 files)	10 min
5 — Local clones	5 min
6 — Re-share links	2 min
7 — Verification	10 min
Total	~60 min