chore: untrack tesla_fleet_api.egg-info build artifacts - #133
Merged
Conversation
Committed egg-info files dirty the working tree on any local build. Add *.egg-info/ to .gitignore.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Committed
tesla_fleet_api.egg-info/files dirty the working tree on any local build, since setuptools regenerates them. Untracked the directory and added*.egg-info/to.gitignore.No other generated build artifact (
dist/,build/,.pytest_cache, etc.) was tracked — checked while in there.Full validation pipeline is skipped per the standing small-change rule for low-risk tooling changes; ruff, pyright, and pytest (707 passed) were run locally and pass. Verified
uv buildtwice leavesgit statusclean.