Streamline use of pre-commit in GitHub workflows#1186
Streamline use of pre-commit in GitHub workflows#1186jakob-keller merged 2 commits intoaio-libs:masterfrom
pre-commit in GitHub workflows#1186Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1186 +/- ##
=======================================
Coverage 86.94% 86.94%
=======================================
Files 64 64
Lines 5983 5983
=======================================
Hits 5202 5202
Misses 781 781
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
e646c69 to
d820298
Compare
|
It's usually good to move it into the regular CI/CD workflow. pre-commit.ci has some limitations when it comes to linters needing network access or external environments (which can be the case for pylint). |
d820298 to
1856ef6
Compare
|
Pre PR we were running pre-commit hooks up to three times on GitHub:
This PR would run 1. across the entire matrix (currently Python 3.8 - 3.13) and remove 2. Further improvements, such as introducing tox, are out of scope of this PR. |
pre-commitpre-commit in GitHub workflows
1856ef6 to
c4b6995
Compare
Description of Change
Assumptions
pre-commitin GitHub workflows #1186 (comment)Checklist for All Submissions
Checklist when updating botocore and/or aiohttp versions