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 #1170

Closed
wants to merge 1 commit into from

Conversation

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0](pre-commit/pre-commit-hooks@v4.6.0...v5.0.0)
- [github.com/astral-sh/ruff-pre-commit: v0.5.7 → v0.6.9](astral-sh/ruff-pre-commit@v0.5.7...v0.6.9)
- [github.com/pre-commit/mirrors-eslint: v8.56.0 → v9.12.0](pre-commit/mirrors-eslint@v8.56.0...v9.12.0)
- [github.com/crate-ci/typos: v1.23.6 → v1.26.0](crate-ci/typos@v1.23.6...v1.26.0)
@coveralls
Copy link

Coverage Status

coverage: 90.478%. remained the same
when pulling 599a0e1 on pre-commit-ci-update-config
into 1cdcf9e on main.

@MyPyDavid
Copy link
Member

this one goes to main because there currently no ci config in the .pre-commit-config.yaml on main, right?

@afuetterer
Copy link
Member

Yes. It uses the defaults. Maybe you should merge the config file into main as a hotfix shortcut. If 2.3 takes a couple of months, you will get a few of these.

@MyPyDavid
Copy link
Member

Yes. It uses the defaults. Maybe you should merge the config file into main as a hotfix shortcut. If 2.3 takes a couple of months, you will get a few of these.

alright, I've opened a PR for that #1172

@MyPyDavid MyPyDavid closed this Oct 18, 2024
@MyPyDavid MyPyDavid deleted the pre-commit-ci-update-config branch October 18, 2024 08:13
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.

3 participants