- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Merge main into v3 #1203
Merge main into v3 #1203
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…vate/all chore(deps): update all dependencies
…vate/major-all chore(deps): update all dependencies (major)
for more information, see https://pre-commit.ci
…vate/all chore(deps): update all dependencies
for more information, see https://pre-commit.ci
…vate/lock-file-maintenance chore(deps): lock file maintenance
…tion_django
…_return_type
for more information, see https://pre-commit.ci
…vate/all chore(deps): update all dependencies
for more information, see https://pre-commit.ci
…vate/lock-file-maintenance chore(deps): lock file maintenance
…-optional Make docs dependencies non optional again
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
Were there still conflicts after my last pass ? Nothing too complex I hope ? |
Nope, minor. I struggled more with the .pre-commit-config.yml constantly got overridden (for one hour or so 😂). But then, at some point, I realized how poetry-to-pre-commit works 😉. |
Oh wow, sorry for the time loss ! Do you think we should write about that in CONTRIBUTING.md ? |
It's not too bad. As a result, I learned a bit about pre-commit, which also benefits my other projects. I can add a little hint to the docs, on the other hand we can't document everything. |
Pull main into v3, solve conflicts. Also, updated dependencies.
Successful PR Checklist:
PR label(s):