I often observe PRs with minor changes to application code or unit tests, but no changes to dependencies, and a uv.lock change is pushed. This uv.lock change is unnecessary, and pollutes the Git history for this uv.lock.
How do we feel about adding a pre-commit hook or GitHub Action to detect uv.lock changes?
I define an unnecessary uv.lock change as something like (I know this isn't exact, but you get the idea):
# Previously, uv.lock has changes on the Git branch `feature`
git checkout feature
git checkout main -- uv.lock
uv lock
if git diff main -- uv.lock; then
echo "uv.lock change should be reverted."
fi
I often observe PRs with minor changes to application code or unit tests, but no changes to dependencies, and a
uv.lockchange is pushed. Thisuv.lockchange is unnecessary, and pollutes the Git history for thisuv.lock.How do we feel about adding a
pre-commithook or GitHub Action to detectuv.lockchanges?I define an unnecessary
uv.lockchange as something like (I know this isn't exact, but you get the idea):