chore: untrack compiled bytecode and add a .gitignore - #121
Merged
Conversation
13 .pyc files were committed, and the repo had no .gitignore at all, so every local test run showed them as modified. That is noise on every branch, and it caused stray diffs while working in this clone. git rm --cached only, so nothing is deleted from working copies. The .gitignore covers bytecode plus the usual build and tool-cache directories, three of which (.mypy_cache, .pytest_cache, .ruff_cache) are already present untracked here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
What
13
.pycfiles are committed to this repository, and there is no.gitignoreat all:So any local
pytestrun rewrites tracked files and they show up as modified on every branch. I hit this while working in this clone:git statusshowed seven modified.pycfiles I had not touched, which is exactly the kind of noise that ends up in an unrelated commit by accident.Two of the test artifacts are stale in a way that shows the problem:
test_modelsis committed twice, once built by pytest 9.0.3 and once by 9.1.1.What this does
git rm --cachedon all 13. Nothing is deleted from working copies, the files stay on disk and are simply no longer tracked..gitignorecovering bytecode, build artifacts, and tool caches. Three of the cache directories it lists (.mypy_cache,.pytest_cache,.ruff_cache) are already sitting untracked in this repo.No source, spec, or test content is touched.
Deliberately separate from #120 so a docs amendment under a 14-day comment period does not carry unrelated hygiene with it.
🤖 Generated with Claude Code