holman/dotfiles

@holman does dotfiles

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 15th, 2010
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 3,214
Total Stargazers: 7,771 (+0)
Total Subscribers: 139 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 2.4 days
90th percentile: 2.4 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,846 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Holman does dotfiles is a shell configuration framework designed to organize and manage dotfiles through a topic-centric structure.

The project solves the problem of scattered, disorganized dotfiles by grouping related configurations into topic directories. Rather than maintaining monolithic alias files or scattered configuration across the home directory, the framework lets you create topic folders like "ruby" or "git" and automatically processes files based on their extensions. Files ending in .zsh are loaded into your shell environment, files ending in .symlink are symlinked into your home directory during bootstrap, and executable scripts named install.sh run during installation. This approach keeps all configurations version-controlled in a single dotfiles directory while maintaining the expected file locations throughout your system.

You should adopt this if you want a lightweight, fork-friendly way to manage shell configurations across machines. The project explicitly encourages forking and customization—you remove what you don't need and build on what you do. It works well for developers who use zsh and want to organize their setup by functional area rather than by file type. The framework is particularly suited to those who value simplicity and transparency; the bootstrap and installation scripts are straightforward shell code you can read and modify. The README does not compare this approach to alternatives, but it does emphasize that the philosophy is to make dotfiles meant to be forked rather than treated as a finished product.

The project maintains an open stance toward bug reports and issues, with the maintainer explicitly welcoming reports from new users who encounter blockers and committing to fix them. The codebase is actively used as the maintainer's personal dotfiles, which means real-world usage drives changes but also carries the risk that personal workflow adjustments might occasionally break things for others if dependency checks are overlooked.