-
Notifications
You must be signed in to change notification settings - Fork 0
Runbooks
Preferred path:
- Open Safety → Backups in CodingBuddy.
- Select the backup.
- Review the Current/Backup preview.
- Choose Restore…. CodingBuddy backs up the current target before writing the selected backup through its safe writer.
Manual fallback:
ls -t ~/Library/Application\ Support/CodingBuddy/Backups/zshrc-*
cp ~/Library/Application\ Support/CodingBuddy/Backups/zshrc-<timestamp> ~/.zshrcBackups are plain copies of the pre-write state; the newest 20 per file are kept. The UI restore only enables backups whose filename maps to a known CodingBuddy-managed target, because older backup filenames do not store full original paths.
defaults delete apps3k.CodingBuddydefaults write apps3k.CodingBuddy flag.<name> -bool YES # or NO
defaults delete apps3k.CodingBuddy flag.<name> # back to channel defaultThe wiki is overwritten from docs/wiki/ on every merge to main. If someone edited the wiki directly and the edit was lost: recover it from the wiki's git history (git clone https://github.com/apps3k-com/CodingBuddy.wiki.git) and re-apply it as a PR against docs/wiki/.
- Check the
release-pleaseaction run on the last push tomain. - Verify the commits since the last tag are Conventional (
git log --oneline $(git describe --tags --abbrev=0)..). - release-please ignores
docs:/chore:/ci:commits for version bumps — a release PR only appears forfeat:/fix:(or breaking) commits.
If GitHub's hosted macos-26 image is unavailable, switch runs-on in .github/workflows/ci.yml to the newest available macOS image and pin Xcode 26 via xcode-select.
Source of truth: docs/wiki/ in the main repo · edit via pull request · synced here automatically on merge.
📘 User Documentation
🔧 Technical (EN)