chore: ignore .serena/ and claudedocs/ - #57
Merged
Conversation
Both are agent tooling scratch that lands in the repo root — Serena's project cache and generated analysis write-ups. Neither is an input to a build, a test or the docs site, and both showed up as untracked noise in every `git status` during #52. They go here rather than in a personal excludes file for the same reason .superpowers/ already does: a global exclude is not inherited, so a second contributor running the same tooling would see the same noise and have to rediscover the fix. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NhqNRBg83czKfr8L6FF5xf
fsecada01
added a commit
that referenced
this pull request
Aug 1, 2026
Picks up #56 (the daisy CDN fix) and #57 (the gitignore chore). One conflict, in CHANGELOG.md, and it was purely additive: both sides appended a new section under [Unreleased] and neither contradicts the other. Both kept, newest first — #54's Added/Fixed pair above #56's. Renamed master's bare `### Fixed` to `### Fixed — daisyUI's CDN recipe was missing its utility layer (#56)`. Every other heading in the file carries the em-dash summary, and after this merge there are two `Fixed` sections side by side, so a bare one is ambiguous as well as inconsistent. Content is verbatim from master. Gate on the merged tree: 2311 passed, 13 skipped · ruff check and ruff format --check clean on src tests · djlint 0 errors on both template trees · mkdocs build --strict clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NhqNRBg83czKfr8L6FF5xf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both are agent tooling scratch that lands in the repo root — Serena's project cache and generated analysis write-ups. Neither is an input to a build, a test or the docs site, and both showed up as untracked noise in every
git statusduring #52.They go in the repo's
.gitignorerather than a personal excludes file for the same reason.superpowers/already does: a global exclude is not inherited, so a second contributor running the same tooling would see the same noise and have to rediscover the fix.Verified with
git check-ignore -v— both paths now resolve to the new rules, andgit statusis clean.🤖 Generated with Claude Code
https://claude.ai/code/session_01NhqNRBg83czKfr8L6FF5xf