astral-sh / astral-sh/uv-pre-commit
uv-export behavior
- Dominant language
- Python
- Stars
- 348
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for this helpful pre-commit plugin.
One thing I noticed was that uv-export is marked as "passed" even if it generates a brand new requirements file. I'd expect it to only pass if it creates no new changes, and to fail (and force me to add requirements then recommit) otherwise. Is there a way to enable that behavior?
Thanks!
Dan
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the uv-export hook and how it determines a passed result after generating a requirements file. Check for tests covering generated requirements files; done means a newly created or changed requirements file causes the hook to fail so it must be added before recommitting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100