Skip to content

fix: correct dotfiles clone path in raspi set.sh - #6

Draft
LJLee37 wants to merge 1 commit into
raspifrom
claude/settingfiles-restructure-raspi-arch-uk2buw-raspi
Draft

fix: correct dotfiles clone path in raspi set.sh#6
LJLee37 wants to merge 1 commit into
raspifrom
claude/settingfiles-restructure-raspi-arch-uk2buw-raspi

Conversation

@LJLee37

@LJLee37 LJLee37 commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Summary

Part of a repo-wide cleanup (companion PRs on master, arch, macOS, ubuntu, alpine, plus a new raspi-arch branch — see that PR for the Arch Linux ARM install, and the master PR for the full rationale on the shared-file documentation approach).

  • Bug fix: set.sh hard-coded ~/gitRepos/Personal/settingfiles while README instructs cloning to ~/gitRepos/settingfiles, so following the README broke set.sh on this branch. Standardized on ~/gitRepos/settingfiles.
  • Docs: Added the branch table / repo-structure explanation, plus a short "install order" section (install.shset.sh → optional backup.sh) that wasn't documented anywhere before.

No other content changes — .vimrc/.zshrc/init.vim are untouched.

Hardcoded personal values (found on this branch, left untouched)

  • git identity: user.name "LJLee37", user.email "ljlee3759@gmail.com" (install.sh)
  • GPG signing key 8090E75C56E49652 (install.sh)
  • LAN backup destination 192.168.35.203 (backup.sh) — worth double-checking this is still the right host before relying on backup.sh
  • username ljlee (path assumptions in backup.sh)

Test plan

  • grep -n 'gitRepos/settingfiles' set.sh shows both cp lines updated, no remaining Personal/ references
  • README renders correctly

Generated by Claude Code

set.sh hard-coded ~/gitRepos/Personal/settingfiles while README says
to clone to ~/gitRepos/settingfiles; standardize on the README path.

Also document the branch-per-OS layout and this branch's install
order in README.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants