Update UV lockfile handling instructions

Improved the documentation comment regarding `.uv.lock` file inclusion in version control. The updated comment now emphasizes the importance of including `.uv.lock` for binary package reproducibility while also advising on ignoring it for libraries or packages that run in multiple environments.
This commit is contained in:
p3ngu1nZz 2025-01-29 05:35:02 -05:00 committed by GitHub
parent d5ac09e92f
commit 671164c90a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -82,6 +82,12 @@ target/
profile_default/ profile_default/
ipython_config.py ipython_config.py
# uv
# Similar to Pipfile.lock and poetry.lock, it is recommended to include `.uv.lock` in version control.
# This ensures reproducibility, especially for binary packages. However, for libraries or packages that run in multiple environments,
# you might prefer to ignore this file and check it in only if necessary.
# .uv.lock
# pyenv # pyenv
# For a library or package, you might want to ignore these files since the code is # For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in: # intended to run in multiple environments; otherwise, check them in: