Ignore uv.lock: a test-run byproduct, not a consumed lock file

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01731mKtVzsfeT4Vi3TvkR48
This commit is contained in:
Claude
2026-08-13 14:44:58 +00:00
parent b1cdc3d55d
commit 44d1387007
+3 -4
View File
@@ -98,10 +98,9 @@ ipython_config.py
# Pipfile.lock
# UV
# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
# This is especially recommended for binary packages to ensure reproducibility, and is more
# commonly ignored for libraries.
# uv.lock
# Deployment installs via `pip install .` (Dockerfile), so no lock file is consumed
# anywhere; a uv.lock is just a byproduct of running the test suite through `uv run`.
uv.lock
# poetry
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.