k #1
Open
k #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
updates: - [github.com/asottile/setup-cfg-fmt: v1.20.0 → v1.20.1](asottile/setup-cfg-fmt@v1.20.0...v1.20.1) - [github.com/asottile/add-trailing-comma: v2.2.1 → v2.2.2](asottile/add-trailing-comma@v2.2.1...v2.2.2)
…e-config [pre-commit.ci] pre-commit autoupdate
adjust error outputs to be more standardized
updates: - [github.com/asottile/pyupgrade: v2.31.1 → v2.32.0](asottile/pyupgrade@v2.31.1...v2.32.0)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/add-trailing-comma: v2.2.2 → v2.2.3](asottile/add-trailing-comma@v2.2.2...v2.2.3)
…e-config [pre-commit.ci] pre-commit autoupdate
Document --assume-in-merge in README
…merge-conflict-doc Document check-merge-conflict argument
There was already a guard preventing the check-executables-have-shebangs hook from raising false positives on win32 by looking up the Git file mode rather than relying on the file mode in the file system. Git already automatically probes the file system for executable bit support. Leverage Git's core.fileMode config variable to prevent false positives on all file systems that don't track executable bits.
updates: - [github.com/asottile/reorder_python_imports: v3.0.1 → v3.1.0](asottile/reorder-python-imports@v3.0.1...v3.1.0) - [github.com/pre-commit/mirrors-mypy: v0.942 → v0.950](pre-commit/mirrors-mypy@v0.942...v0.950)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/pyupgrade: v2.32.0 → v2.32.1](asottile/pyupgrade@v2.32.0...v2.32.1)
…e-config [pre-commit.ci] pre-commit autoupdate
…e-mode-false Check Git core.fileMode rather than infer from OS.
Add instruction to change executable mode on windows
updates: - [github.com/pre-commit/mirrors-mypy: v0.950 → v0.960](pre-commit/mirrors-mypy@v0.950...v0.960)
…e-config [pre-commit.ci] pre-commit autoupdate
Use tomli and tomllib instead of toml
looks like this was accidentally running on `commit-msg` hooks
set stages for `check-added-large-files`
name-test-tests: add --pytest-test-first convention
updates: - [github.com/asottile/pyupgrade: v2.32.1 → v2.34.0](asottile/pyupgrade@v2.32.1...v2.34.0) - [github.com/pre-commit/mirrors-mypy: v0.960 → v0.961](pre-commit/mirrors-mypy@v0.960...v0.961)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/reorder_python_imports: v3.1.0 → v3.3.0](asottile/reorder-python-imports@v3.1.0...v3.3.0)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/reorder_python_imports: v3.3.0 → v3.8.1](asottile/reorder-python-imports@v3.3.0...v3.8.1) - [github.com/asottile/pyupgrade: v2.34.0 → v2.37.1](asottile/pyupgrade@v2.34.0...v2.37.1)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/setup-cfg-fmt: v1.20.1 → v1.20.2](asottile/setup-cfg-fmt@v1.20.1...v1.20.2) - [github.com/asottile/reorder_python_imports: v3.8.1 → v3.8.2](asottile/reorder-python-imports@v3.8.1...v3.8.2) - [github.com/asottile/pyupgrade: v2.37.1 → v2.37.2](asottile/pyupgrade@v2.37.1...v2.37.2) - [github.com/pre-commit/mirrors-mypy: v0.961 → v0.971](pre-commit/mirrors-mypy@v0.961...v0.971)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/asottile/setup-cfg-fmt: v1.20.2 → v2.0.0](asottile/setup-cfg-fmt@v1.20.2...v2.0.0) - [github.com/asottile/pyupgrade: v2.37.2 → v2.37.3](asottile/pyupgrade@v2.37.2...v2.37.3) - [github.com/PyCQA/flake8: 4.0.1 → 5.0.2](PyCQA/flake8@4.0.1...5.0.2)
for more information, see https://pre-commit.ci
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/PyCQA/flake8: 5.0.2 → 5.0.4](PyCQA/flake8@5.0.2...5.0.4)
…e-config [pre-commit.ci] pre-commit autoupdate
updates: - [github.com/pre-commit/mirrors-autopep8: v1.6.0 → v1.7.0](pre-commit/mirrors-autopep8@v1.6.0...v1.7.0)
…e-config [pre-commit.ci] pre-commit autoupdate
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.