Skip to content
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 #37

Closed
wants to merge 2 commits into from

Conversation

@codecov
Copy link

codecov bot commented Apr 11, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8f61854) 77.83% compared to head (aaed29f) 77.83%.

❗ Current head aaed29f differs from pull request most recent head 5e2e47b. Consider uploading reports for the commit 5e2e47b to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   77.83%   77.83%           
=======================================
  Files          37       37           
  Lines        2369     2369           
=======================================
  Hits         1844     1844           
  Misses        525      525           
Flag Coverage Δ
pytests 77.83% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from bf0c954 to 2fef86e Compare May 17, 2022 01:17
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 0d04a89 to c345f5c Compare June 13, 2022 23:52
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 7b01ccc to 34375d2 Compare July 5, 2022 00:02
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 3ec6672 to 4498c69 Compare August 9, 2022 00:26
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from b35debe to 555359d Compare September 6, 2022 01:05
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 4c2c88d to 1e88be2 Compare October 11, 2022 02:12
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from d5f63e5 to 129e190 Compare November 29, 2022 03:46
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 2955888 to 5380ec5 Compare December 13, 2022 03:12
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 6979612 to b670b0d Compare December 20, 2022 03:18
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 4fe10ea to bcce5fa Compare December 27, 2022 04:12
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from aaed29f to 160381e Compare January 31, 2023 05:48
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 461f6c8 to 89bfb85 Compare February 7, 2023 07:06
Copy link
Collaborator

@JPchico JPchico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests in this are broken, but this has nothing to do with the changes in this PR and more with the out of date status of the package. What do you think is the best course of action @chrisjsewell . I think merge and then solve any conflicts when pushing the new release. Or one can wait for the new release and the merge this.

@chrisjsewell
Copy link
Member

yeh I would just ignore this PR and continue on with getting develop into master

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from dbfb877 to 457622e Compare April 4, 2023 09:18
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from c54215a to 6303b8a Compare July 11, 2023 09:53
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from f98ad29 to 0f11b42 Compare August 1, 2023 12:03
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from a1ded28 to 9d969b2 Compare September 12, 2023 12:48
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 0483a2e to 434df30 Compare October 9, 2023 21:50
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from f08bddc to db64256 Compare October 23, 2023 21:40
updates:
- git://github.com/pre-commit/pre-commit-hooks → https://github.com/pre-commit/pre-commit-hooks
- [github.com/pre-commit/pre-commit-hooks: v3.2.0 → v4.5.0](pre-commit/pre-commit-hooks@v3.2.0...v4.5.0)
- https://github.com/timothycrosley/isorthttps://github.com/PyCQA/isort
- [github.com/PyCQA/isort: 5.5.3 → 5.12.0](PyCQA/isort@5.5.3...5.12.0)
- [github.com/psf/black: 20.8b1 → 23.11.0](psf/black@20.8b1...23.11.0)
- https://gitlab.com/pycqa/flake8https://github.com/PyCQA/flake8
- [github.com/PyCQA/flake8: 3.8.3 → 6.1.0](PyCQA/flake8@3.8.3...6.1.0)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 7ff9730 to d4575fc Compare November 13, 2023 21:49
@sphuber sphuber deleted the pre-commit-ci-update-config branch November 28, 2023 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants