Merge branch 'develop' into feature/repo-sync
# Conflicts: # .claude/memory/journal.md
This commit is contained in:
@@ -117,3 +117,6 @@ Done: window-style / window-active-style added. Two traps: colour234 ≈ iTerm2
|
||||
|
||||
## 2026-10-07 (pm) — repo-sync: multi-forge repo tree
|
||||
Done: `bin/repo-sync` (gitlab/github/gitea/bitbucket cloud via curl+jq, daily cache, mkdir lock, dedup ns/project) + `repo` fn/completion in 3 rc files + install.sh jq + docs. Port of Alphalink dotfiles `repo`/`repo-reset`. Stub-curl harness caught token shift (IFS tab merges empty field); live GitLab 139 projects in 3s. Decided (chat): name `repo-sync`, tokens in `~/.config/repos/forges.conf` 0600, root `~/repos`, Bitbucket Cloud only. On feature/repo-sync, not finished. BDR/LRN offered, not written.
|
||||
|
||||
## 2026-10-07 (2) — macOS zsh default, remote-install prompts
|
||||
Done: choose_macos_shell default bash → zsh (Enter, no tty, unknown value). Found: `curl | bash` path never asked USER/EMAIL (stdin = pipe → `[ -t 0 ]` false → login name + empty email, bash, no offers); remote-install.sh now runs install.sh `</dev/tty` when openable. Found: BRANCH default `master`, origin has only `main` (raw URL 404) → `main`. Lint OK, chooser tested 4 values. Branch feature/macos-zsh-default, not merged. Other session: feature/repo-sync open (CLAUDE.md layout already lists repo-sync).
|
||||
|
||||
Reference in New Issue
Block a user