fix: remove uv.lock from .gitignore to track dependency versions #3
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
uv.lockfrom.gitignoreto ensure consistent dependency versions across all environmentsRationale
The
uv.lockfile should be committed to version control as it:package-lock.jsonin npm orCargo.lockin Rust)Changes
uv.lockentry from.gitignoreTest Plan
.gitignoreis updated correctlyuv.lockfile is affecteduv.lockfiles will be properly tracked by Git