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.

Sign up for GitHub

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

Jump to bottom

[pre-commit.ci] pre-commit autoupdate #24

Merged
merged 2 commits into from
May 21, 2024
Merged

[pre-commit.ci] pre-commit autoupdate #24

merged 2 commits into from
May 21, 2024

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Jun 6, 2023 •
edited
Loading

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 14d83f8 to 55ee380 Compare July 4, 2023 04:38
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from d06d8f3 to 3a282d3 Compare August 1, 2023 06:26
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from f4835da to 7435048 Compare October 3, 2023 08:14
@coveralls
Copy link

coveralls commented Nov 6, 2023 •
edited
Loading

Pull Request Test Coverage Report for Build 8976039859

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 53.125%
Totals Coverage Status
Change from base Build 8690749033: 0.0%
Covered Lines: 17
Relevant Lines: 32
💛 - Coveralls

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 115ec36 to 9b125aa Compare January 1, 2024 19:53
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 6ffc74b to 757018f Compare April 1, 2024 21:35
@pre-commit-ci
[pre-commit.ci] pre-commit autoupdate
be15265 
updates:
- [github.com/psf/black: 23.3.0 → 24.4.2](psf/black@23.3.0...24.4.2)
- [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/pycqa/isort: 5.12.0 → 5.13.2](PyCQA/isort@5.12.0...5.13.2)
- [github.com/PyCQA/flake8: 6.0.0 → 7.0.0](PyCQA/flake8@6.0.0...7.0.0)
- [github.com/pre-commit/mirrors-mypy: v1.2.0 → v1.10.0](pre-commit/mirrors-mypy@v1.2.0...v1.10.0)
- [github.com/codespell-project/codespell: v2.2.4 → v2.2.6](codespell-project/codespell@v2.2.4...v2.2.6)
- [github.com/asottile/pyupgrade: v3.3.2 → v3.15.2](asottile/pyupgrade@v3.3.2...v3.15.2)
- [github.com/asottile/setup-cfg-fmt: v2.2.0 → v2.5.0](asottile/setup-cfg-fmt@v2.2.0...v2.5.0)
- [github.com/pre-commit/mirrors-prettier: v3.0.0-alpha.9-for-vscode → v4.0.0-alpha.8](pre-commit/mirrors-prettier@v3.0.0-alpha.9-for-vscode...v4.0.0-alpha.8)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 07166b0 to be15265 Compare May 6, 2024 21:28
@GuillermoFidalgo
Copy link

@klieret should I ignore the building checks and merge?

@klieret
Copy link
Member

klieret commented May 13, 2024

sure, absolutely harmless. Not sure if testing was ever properly set up here

@GuillermoFidalgo GuillermoFidalgo merged commit 6bfef8c into main May 21, 2024
3 of 7 checks passed
@GuillermoFidalgo GuillermoFidalgo deleted the pre-commit-ci-update-config branch May 21, 2024 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@coveralls @GuillermoFidalgo @klieret