Skip to content

Commit uv.lock and fix the two dead .gitignore lines - #12

Merged
erxxc merged 1 commit into
mainfrom
chore/commit-uv-lock
Sep 9, 2026
Merged

erxxc merged 1 commit into
mainfrom
chore/commit-uv-lock

Conversation

@erxxc

@erxxc erxxc commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • .gitignore listed uv.lock and .python-version with trailing # committed comments. gitignore has no trailing-comment syntax, so those lines matched nothing: the lockfile was neither ignored nor committed, and every uv sync left an untracked uv.lock behind.
  • Replaces the two lines with a comment explaining why they must not be listed, and commits the uv.lock that uv sync --extra dev produces on Python 3.11 (per .python-version), so dependency resolution is reproducible as docs/offline-development.md already says it should be.

CI installs with pip, so the lockfile does not change what CI runs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SrGsKknvZvNgFwvTVnHdUA

.gitignore listed `uv.lock` and `.python-version` with trailing
"# committed" comments. gitignore has no trailing-comment syntax, so
those patterns matched nothing: uv.lock was neither ignored nor
committed, and every `uv sync` left an untracked lockfile behind.

Replace the two lines with a comment explaining why they must not be
listed, and commit the lockfile that `uv sync --extra dev` produces on
Python 3.11 (per .python-version), so dependency resolution is
reproducible as docs/offline-development.md already says it should be.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SrGsKknvZvNgFwvTVnHdUA
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant