Daily Workflow
After installation, your live config files are symlinks into this repository. That means you can edit your normal config paths and still keep everything versioned in Git.
Start A Development Session
Open WezTerm, move to a project, and choose a layout:
cd "$HOME/Projects/example"
tmux-dev exampleUse the first pane for Neovim and the second for tests or a development server:
nvim .For four simultaneous commands:
tmux-agent example-agents "$HOME/Projects/example"Detach with Ctrl+a, then d. Return later with:
tmux attach -t exampleThe application pages explain how terminal tabs, tmux windows, tmux panes, and Neovim buffers differ.
Update Local Configs
Pull the latest changes and run diagnostics:
bbldr dotfiles updateThe command updates only packages that are already linked. If an update adds a new configuration file to one of those packages, update creates the missing link; when a tracked file is removed, its obsolete project link is removed. It does not enable unrelated packages or move neighboring local files.
Update refuses to run when local files have uncommitted changes. Commit or stash them first.
Edit Configs
These paths are managed by the repo:
~/.config/nvim
~/.config/wezterm
~/.tmux.conf
~/.local/bin/tmux-dev
~/.local/bin/tmux-agent
~/.local/bin/tmux-status
~/.zshrcYou can edit either the live path or the repo path. Both point to the same tracked files.
Example
Editing ~/.tmux.conf changes ~/.config/dotfiles/tmux/.tmux.conf.
Reload Changes
Some tools need to reload their config after editing.
| Tool | Reload command |
|---|---|
| Zsh | source ~/.zshrc |
| tmux | tmux source-file ~/.tmux.conf |
| WezTerm | Cmd+R inside WezTerm |
| Neovim | Restart Neovim, or source the relevant Lua file manually. |
Save Changes
Review, commit, and push:
cd ~/.config/dotfiles
git status --short
git diff
git add -- <files>
git commit -m "Update dotfiles"
git pushCheck Before Publishing
Run:
bbldr dotfiles doctor
bbldr dotfiles packages
bbldr dotfiles check
git status --shortBefore pushing, review every staged file:
git diff --cachedDo not publish secrets
Never commit API keys, tokens, SSH keys, local databases, credentials, or machine-specific private paths.
Typical Change Flow
- Edit a config file.
- Reload the app.
- Test the behavior.
- Review the Git diff.
- Commit the change.
- Push it to GitHub.
nvim ~/.tmux.conf
tmux source-file ~/.tmux.conf
cd ~/.config/dotfiles
git diff
git add -- tmux/.tmux.conf
git commit -m "Update tmux config"
git push