[pre-commit.ci] pre-commit autoupdate #111
Conversation
![pre-commit-ci[bot]](https://avatars.githubusercontent.com/in/68672?s=60&v=4){kind=small}
updates: - [github.com/pre-commit/pre-commit-hooks: v4.0.1 → v4.4.0](pre-commit/pre-commit-hooks@v4.0.1...v4.4.0) - [github.com/pycqa/flake8: 3.9.2 → 6.0.0](PyCQA/flake8@3.9.2...6.0.0) - [github.com/pycqa/isort: 5.9.3 → 5.12.0](PyCQA/isort@5.9.3...5.12.0) - [github.com/psf/black: 21.7b0 → 23.3.0](psf/black@21.7b0...23.3.0) - [github.com/pre-commit/mirrors-mypy: v0.910 → v1.4.1](pre-commit/mirrors-mypy@v0.910...v1.4.1) - [github.com/asottile/pyupgrade: v2.23.1 → v3.8.0](asottile/pyupgrade@v2.23.1...v3.8.0)
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
0a7f008
to
aaeedef
Compare
for more information, see https://pre-commit.ci
|
Hm seems some typing is off? 
|
|
Would need to get the latest dev changes to master @bbelderbos :) |
|
Also quick fixed a linting error and vulnerability of requests. @bbelderbos could you already test it on slack? can you merge dev to master? |
|
@pogross changed base branch to develop which has latest code to have tests run against that. I logged into test slack (called "SlackBotTest" or "slackbottest-gruppe") but last time it did not work, gonna read up on how to have the uat code (that has latest develop code with your last changeset), connect properly with that slack. |
|
Resolved merge conflict |
|
@pogross not sure why some tests did not complete, but the changes here should not impact performance. I was able to run through README and set up a new karmabot in a test slack and develop branch works 🎉 
So let me merge all to master and push to prod and validate it works there too ... Thanks for your patience, this clearly got on the backburner 😅 |
updates: