CI: temporarily disable pre commit #219
Merged
Conversation
This file contains 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
unkcpz
force-pushed
the
ci/temprarily-disable-pre-commit
branch
from
4e1a7f0
to
1630a15
Compare
csadorf
suggested changes
Mar 30, 2022
unkcpz
force-pushed
the
ci/temprarily-disable-pre-commit
branch
from
1630a15
to
12fceb4
Compare
- Remove workaround, after problem described in #206 (comment) is resolved. - new psf/black version for issue psf/black#2964 (comment)
unkcpz
force-pushed
the
ci/temprarily-disable-pre-commit
branch
from
12fceb4
to
2be1c0e
Compare
|
@csadorf Sorry, yes, it was failed, sadly. I didn't comment the pre-commit part out since |
csadorf
approved these changes
Mar 30, 2022
|
@csadorf thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As described in #206 (comment), the ci test failed since an installation issue.
Temporarily disabled it and enable it after it is fixed on pre-commit side.Pining virtualenv version to workaround, which needs to be removed after issue fixed.