Add uv.lock to gitattributes

[NicolaCourtier]

Description

Hide changes to the auto-generated uv.lock file by default.

Issue reference

Show fix

Review

Before you mark your PR as ready for review, please ensure that you've considered the following:

• Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
• Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

• New Feature: A non-breaking change that adds new functionality.
• Optimization: A code change that improves performance.
• Examples: A change to existing or additional examples.
• Bug Fix: A non-breaking change that addresses an issue.
• Documentation: Updates to documentation or new documentation for new features.
• Refactoring: Non-functional changes that improve the codebase.
• Style: Non-functional changes related to code style (formatting, naming, etc).
• Testing: Additional tests to improve coverage or confirm functionality.
• Other: (Insert description of change)

Key checklist:

• No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
• All unit tests pass: $ nox -s tests
• The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

• Code is well-commented, especially in complex or unclear areas.
• Added tests that prove my fix is effective or that my feature works.
• Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

[agriyakhetarpal]

Hi @NicolaCourtier, I would suggest not ignoring uv.lock in version control – it's generally recommended to include it in version control for reproducibility (as the comment you added is saying). If you're looking to reduce the increased diff on PRs generated when the lockfile is changed, you could add

uv.lock linguist-generated=true

to the .gitattributes file, which will make GitHub not show the diff automatically unless you prompt it to.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.21%. Comparing base (df79ec2) to head (deff4b7).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #695   +/-   ##
========================================
  Coverage    99.21%   99.21%           
========================================
  Files           67       67           
  Lines         4842     4842           
========================================
  Hits          4804     4804           
  Misses          38       38           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[NicolaCourtier]

Thanks for the advice @agriyakhetarpal !

[agriyakhetarpal]

Thanks, @NicolaCourtier!

You can see that this works now, on https://github.com/pybop-team/PyBOP/pull/695/files :)