Repository navigation
Human action 168
Canonical issue: #168. Decided by ADR-0039 §7, step 5.
The product is causet, and its records, refs and command already carry the name (#159). This
renames the last two things only the owner can: the GitHub repository jwh3times/causet becomes
jwh3times/causet, and project 7 becomes "causet".
- Owner role: repository admin and owner of project 7.
- Time: about 10 minutes.
-
The name is free. Confirm that
https://github.com/jwh3times/causetreturns 404, or thatgh repo view jwh3times/causetfails with "Could not resolve". It did on 2026-09-29. - Nothing is in flight. No release, CI dispatch or open landing is running.
- What moves and what doesn't. GitHub moves issues, PRs, the wiki, Actions history and stars with the repository. It redirects web, Git and API URLs from the old name. Published npm releases keep their old repository URL, which is harmless.
-
Rename the repository. Open
https://github.com/jwh3times/causet/settings, then General, then Repository name. Entercausetand choose Rename.-
Expected: the page reloads at
https://github.com/jwh3times/causet/settings.
-
Expected: the page reloads at
-
Rename the project. Open
https://github.com/users/jwh3times/projects/7/settings. Set Project name tocausetand save. Leave its visibility Private.- Expected: the board header reads "causet".
-
Repoint every maintained clone. On each machine, in each checkout (at least
C:/dev/vcs-lab, plus any POSIX or Orca checkouts), run:git remote set-url origin https://github.com/jwh3times/causet.git git fetch origin git status -sb # expected: the same branch state as before, now tracking the new URL -
Optional: rename local directories and tooling. Each of these costs something, so it is your choice:
-
Renaming the checkout directory (for example
C:/dev/vcs-labtoC:/dev/causet) resets Claude Code's per-project memory, which is keyed by path. Rename only if you accept that. The agent can recreate the essentials from the repository and issues. -
The Proton Drive handoff key
vcs-labinhandoff_map.jsonfollows the checkout directory's name. Rename it together with the directory, or not at all. -
Benchmark host labels (
lab-windows-a) are unaffected.
-
Renaming the checkout directory (for example
gh repo view jwh3times/causet --json nameWithOwner,url,visibility
git ls-remote https://github.com/jwh3times/causet.git HEAD # still answers through the redirect
git -C <each checkout> remote get-url origin # https://github.com/jwh3times/causet.git-
Pass: the repository resolves under the new name, the old URL still answers, project 7 is
titled "causet" and still private, and every checkout's
originuses the new URL. - Partial: a checkout you could not reach counts as partial. Name it on the issue.
- Rename refused because the name is taken: stop, and do not choose another name. Record it on #168: the name is part of ADR-0038 and ADR-0039, so it needs a decision.
-
Rename done but something looks wrong: a repository can be renamed back from the same
settings page. GitHub keeps redirecting both names until a new repository takes the old one.
Do not create a new repository called
vcs-lab, because that breaks the redirect.
- Comment "renamed" on #168 with the verification output.
- An agent then updates the in-repository links in one PR linked from #168:
-
github.com/jwh3times/causetbecomesgithub.com/jwh3times/causetin the README,docs/,package.json(repository,homepage,bugs, which npm provenance requires before the next publish), badges, and this wiki's absolute links; - "causet project board" becomes "causet project board".
-
- When that PR lands, remove
human-action-requiredfrom #168, close it, set its board card to Done, and mark it done in Human TODO.