-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pre-commit.ci] pre-commit autoupdate #89
base: main
Are you sure you want to change the base?
Conversation
f4bbb92
to
3556eaf
Compare
b56d6fe
to
cd9c127
Compare
cd9c127
to
5ca1d8e
Compare
5ca1d8e
to
3a1d6ae
Compare
3a1d6ae
to
3a1f69c
Compare
3a1f69c
to
f73129a
Compare
0bd70e9
to
eba5d42
Compare
eba5d42
to
d97f7b0
Compare
0af94e0
to
90edafb
Compare
2508b30
to
84bb350
Compare
84bb350
to
b0a877f
Compare
b0a877f
to
b6dae24
Compare
b6dae24
to
d008231
Compare
d521cc5
to
24d63ac
Compare
24d63ac
to
0421b63
Compare
0421b63
to
dfed134
Compare
2e12cd2
to
cfe9b50
Compare
5e86d2e
to
0d36963
Compare
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
22055a6
to
a2c4910
Compare
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
5774d57
to
47a4fe0
Compare
eab4e13
to
a109a49
Compare
6096470
to
17f0087
Compare
d4c1871
to
2af3e2a
Compare
13e80de
to
b0a80dd
Compare
93c0b85
to
9c2ceb1
Compare
updates: - [github.com/pre-commit/pre-commit-hooks: v4.4.0 → v4.6.0](pre-commit/pre-commit-hooks@v4.4.0...v4.6.0) - [github.com/psf/black.git: 23.1.0 → 24.8.0](https://github.com/psf/black.git/compare/23.1.0...24.8.0) - [github.com/PyCQA/isort.git: 5.12.0 → 5.13.2](https://github.com/PyCQA/isort.git/compare/5.12.0...5.13.2) - [github.com/PyCQA/flake8.git: 6.0.0 → 7.1.1](https://github.com/PyCQA/flake8.git/compare/6.0.0...7.1.1) - [github.com/pre-commit/mirrors-mypy: v1.0.0 → v1.11.2](pre-commit/mirrors-mypy@v1.0.0...v1.11.2)
ad8d316
to
98a9fb0
Compare
for more information, see https://pre-commit.ci
updates: