tox -e requirements and tox -e precommit are both run via pre-commit and in regular CI.
Besides taking non-negligible time to complete, the only way to fix a failing check would be to include dependency updates as part of the current topic branch, where they IMO don't belong (or wait until they are fixed independently).
Does anybody mind, if we remove those checks from pre-commit and CI?
References
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What do you want to share with us?
tox -e requirementsandtox -e precommitare both run via pre-commit and in regular CI.Besides taking non-negligible time to complete, the only way to fix a failing check would be to include dependency updates as part of the current topic branch, where they IMO don't belong (or wait until they are fixed independently).
Does anybody mind, if we remove those checks from pre-commit and CI?
References
No response
Code of Conduct