-
Notifications
You must be signed in to change notification settings - Fork 684
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
introducing uv in core #4451
base: main
Are you sure you want to change the base?
introducing uv in core #4451
Conversation
Signed-off-by: emdneto <[email protected]>
Signed-off-by: emdneto <[email protected]>
Signed-off-by: emdneto <[email protected]>
Signed-off-by: emdneto <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Signed-off-by: emdneto <[email protected]>
@@ -252,4 +252,4 @@ jobs: | |||
run: pip install tox | |||
|
|||
- name: Run tests | |||
run: tox -e ruff | |||
run: tox -e precommit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think it's weird to have a tox job called pre-commit instead of having the tox job be ruff, and not run pre-commit there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's quite convenient as it runs everything we run locally with pre-commit 😅 Also, you can have the outcome in CI from both ruff commands. If we just use pure ruff command in tox, if the first command fails, the second one won't run.
Description
Same as open-telemetry/opentelemetry-python-contrib#3124
Also, I'm adding a new workflow called
precommit
which now makes more sense. I'm keepingruff
in tox just for convenience for contributors as requested here