Keeping Claude Code Docs Out of the Public Repo with .git/info/exclude — A Design Log on Exclusion and History Management
· 8 min read
If this site helped you, please support us with 🌟 ☕️
When I introduced Claude Code into a personal OSS repository I develop and maintain on my own, a requirement emerged: I wanted to keep the AI-related settings and documentation out of the public repository and operate them locally only. In this post, I focus on the two topics I spent the most time considering — the use cases for exclusion settings, and the design of history management, which tends to become scattered in AI-assisted workflows.
Context and Assumptions
The target is a solo-developed (personal OSS) repository, with branch protection requiring PRs and CI already configured on main / develop. Claude Code is used from within the editor, and the main tasks are refactoring, writing articles, and improving features — repetitive work that mostly stays local.