-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
bump moto #1297
bump moto #1297
Conversation
…sum-streaming-moto-bump # Conflicts: # aiobotocore/httpchecksum.py # requirements-dev.in # tests/test_basic_s3.py # tests/test_patches.py
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1297 +/- ##
==========================================
+ Coverage 87.90% 88.66% +0.75%
==========================================
Files 68 67 -1
Lines 5987 5875 -112
==========================================
- Hits 5263 5209 -54
+ Misses 724 666 -58
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ok finally ready |
btw updated the merge to be squash and merge to avoid master pollution |
This comment was marked as resolved.
This comment was marked as resolved.
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.
Awesome, this one is much overdue!
I have a few minor questions and suggestions, but this should be easy to follow up on.
Thanks for the effort!
thanks for the review! lemme c what I can do about this coverage |
The merge is blocked due to missing verified commit signatures. |
will fix |
@jakob-keller crap it's the pre-commit thing, how do we fix that thing so it's signed? |
I guess the easiest way would be for you to squash the unverified commit and force push your branch. |
The unverified commit originates from https://pre-commit.ci. I don't see a way to make that spit out verified commits. Going forward, I guess we need to either drop pre-commit.ci or drop the verification requirement. I'd be in favor of the former. |
1d773ce
to
1e0264d
Compare
@jakob-keller ya I say drop the pre-commit from being able to modify the PR. Failing is fine, then having the user fix it is better otherwise author may not notice something changing their code on their behalf potentially leading to bugs...like especially since we want to mostly keep formatting from botocore |
No description provided.