-
Notifications
You must be signed in to change notification settings - Fork 15
Use dependency group for dev dependencies #1328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
After tooling support is in, we need to update tox/docs. |
Test results0 tests 0 ✅ 0s ⏱️ Results for commit eaaa229. ♻️ This comment has been updated with latest results. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1328 +/- ##
=======================================
Coverage 78.45% 78.45%
=======================================
Files 124 124
Lines 5458 5458
=======================================
Hits 4282 4282
Misses 1176 1176 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
87e1f74
to
067cf64
Compare
067cf64
to
eaaa229
Compare
|
Scope and purpose
This moves dev dependencies out of
[project.optional-dependencies]
and into[dependency-groups]
. Now we just need to wait for tooling support. See PEP 735.--group
flag for dependency-group parsing forpip-compile
jazzband/pip-tools#2175)Less important:
Contributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Argus can be found in the
Development docs.