Remove committed bytecode and add a .gitignore - #70
Merged
Merged
Conversation
`aec8454` staged `spacecore/functional/` as a directory, which swept 36 `__pycache__` files into the tree. The repository had no `.gitignore`, so nothing stopped it. Untrack them and add the ignore rules that should have been there: bytecode, egg-info, coverage data, build and docs output, local venvs, and `.DS_Store`. Co-Authored-By: Claude Opus 5 <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 this PR does
Untracks 36
__pycache__files that were committed by mistake in #69, and adds the.gitignorethe repository never had.Checklist
pytest tests/ -x -q) — 3766 passed, 170 skipped[Unreleased]— repository hygiene, nothing user-visibleHow it happened
aec8454stagedspacecore/functional/as a directory rather than naming the files it meant, so every__pycache__entry under that path went in with it. With no.gitignorein the repository, nothing caught it.git log --diff-filter=Aattributes all 36 to that one commit; no other unwanted file is tracked anywhere in the tree.What this changes
git rm --cachedon all 36 files. They stay on disk and are regenerated by any run; only the index changes..gitignorecovering bytecode,egg-info, coverage data, build and docs output, local virtualenvs, and.DS_Store.No history rewrite:
0.4.4is shared and already carries the merge, so this is a follow-up commit rather than a force push.Note for review
The
.gitignoreis new, so it is worth a glance for anything you deliberately track that these rules would now hide. I checked the current tree and there is nothing.🤖 Generated with Claude Code