docs: update contribution guide related to uv

[bearomorphism]

It seems that uv sync --dev is not enough. I need to run uv sync --all-groups to have correct environment on my machine.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.88%. Comparing base (4cb3f95) to head (c84d1eb).
⚠️ Report is 3 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1756   +/-   ##
=======================================
  Coverage   97.88%   97.88%           
=======================================
  Files          60       60           
  Lines        2604     2604           
=======================================
  Hits         2549     2549           
  Misses         55       55           

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

[Lee-W]

It seems that uv sync --dev is not enough. I need to run uv sync --all-groups to have correct environment on my machine.

Could you please elaborate on what you want to achieve?

[bearomorphism]

uv sync --dev did not install all required packages for development like ruff in my environment. I spent some time to figure out what was wrong.

I'm not very familiar with uv.

[Lee-W]

It's actually part of PEP 735.

commitizen/pyproject.toml

Lines 89 to 110 in 2e4f4b2

	dev = ["ipython>=8.0", "tox>4", "tox-uv", "poethepoet>=0.34.0"]
	test = [
	"pytest>=7.2",
	"pytest-cov>=4",
	"pytest-mock>=3.10",
	"pytest-regressions>=2.4.0",
	"pytest-freezer>=0.4.6",
	"pytest-xdist>=3.1.0",
	"pytest-gitconfig>=0.9.0",
	]
	linters = [
	"ruff>=0.11.5",
	"pre-commit>=3.2.0",
	"mypy>=1.16.0",
	"types-deprecated>=1.2.9.2",
	"types-python-dateutil>=2.8.19.13",
	"types-PyYAML>=5.4.3",
	"types-termcolor>=0.1.1",
	"types-colorama>=0.4.15.20240311",
	]

What we should use is uv sync --group dev --group test --group linters instead.

or we can use https://packaging.python.org/en/latest/specifications/dependency-groups/#dependency-group-include syntax. something like dev {include-group="test"}, {icnlude-group="linters"}

either ways work better than all-group IMO

[bearomorphism]

I didn't know those. Will take a look.

[noirbizarre]

Oh sorry, I hadn't read this one yet, so I did it in #1763.
So maybe just add the --frozen parameter to avoid dependencies being updated when syncing for contribution.

[bearomorphism]

Thanks!