Stop tracking build/ artifacts and tighten .gitignore - #41
Merged
Conversation
The build/ directory holds regenerated output of `python -m build` (setuptools' build lib), but three copies were committed and had drifted from source (build/lib/veracrypt/__about__.py still read 0.1.0 while src is 0.2.0). Untrack them and ignore build/ going forward so generated artifacts never land in source control. Also tighten two existing rules to match by directory rather than a single hardcoded path: - dist -> dist/ - src/python_veracrypt.egg-info -> *.egg-info/ Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KmtFTMrCghkkNXAkvdXKS2
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
2 participants
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.
Summary
Removes generated build artifacts from source control and closes the
.gitignoregap that let them in.Problem
The
build/directory (setuptools'python -m buildoutput) was partially committed — three files were tracked:Because they're generated, they had already drifted from source:
build/lib/veracrypt/__about__.pystill read__version__ = "0.1.0"whilesrc/veracrypt/__about__.pyis0.2.0. Committed build output like this is noise in diffs and actively misleading.Changes
git rm -r --cached build/— stop tracking the three artifacts (working copy untouched; the dir is regenerated bypython -m build)..gitignore:build/so the artifacts never return.dist→dist/andsrc/python_veracrypt.egg-info→*.egg-info/(match by directory / any egg-info location rather than one hardcoded path).Verification
No source, test, or packaging-config files are affected — this is purely artifact cleanup.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KmtFTMrCghkkNXAkvdXKS2
Generated by Claude Code