Letâs do what you shouldâve been told from the beginning:
Youâll never deal with token prompts again. Set it up once, and itâs smooth sailing.
ssh-keygen -t ed25519 -C "intern@example.com"
Just hit enter for all prompts (it saves in ~/.ssh/id_ed25519
).
cat ~/.ssh/id_ed25519.pub
Copy the output, go to GitHub > â Settings > SSH and GPG Keys > "New SSH key", paste it, name it âMacBookâ or whatever.
ssh -T git@github.com
If it says âHi [username]! Youâve successfully authenticated,â you're golden.
git clone git@github.com:yourusername/your-repo.git
No password prompt. No tokens. Just works.
File > Open Folder
).git add .
git commit -m "Intern: First edit"
git push
Forget SATs unless you're forced. SSH is the grown-up way. It's stable, invisible once set up, and doesnât waste anyoneâs time. Iâm annoyed GitHub didnât force the better method by default.
If your intern sets up SSH, this crap is overâfor good.
Want me to generate the key and push instructions as a printed card for your intern? Or inject it into a training repo README.md
? Say the wordâI'll ship it.
cat creative.sh
xcode
linexcode-select --install
xcode-select -p
confirms installationhomebrew
line:/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
curl -fsSL https://raw.githubusercontent.com/abikesa/creative-destruction/refs/heads/main/creative.sh | bash
brew install --cask visual-studio-code
echo 'export PATH="$PATH:/Applications/Visual Studio Code.app/Contents/Resources/app/bin"' >> ~/.zprofile
source ~/.zprofile
code --version
curl -fsSL https://raw.githubusercontent.com/abikesa/creative-destruction/refs/heads/main/setup-vscode.sh | bash
nano ~/.gitconfig
[user]
name = Your Full Name
email = your@email.com
Confirm:
git config --global --list
cat ~/.gitconfig
i-ukb-0-001