Repository navigation
Commit 4bea7cf
committed
Don't have mypy failure fail the whole tox run
Other environments would still be run even after mypy has failed,
but to avoid having tox runs be unnecessarily inconsistent with the
mypy step in the pythonpackage.yml CI workflow, and also because
GitPython is not currently expected to pass mypy checks, this keeps
mypy errors from causing the whole tox run to be reported as
failed.1 parent 2cc2db7 commit 4bea7cf
1 file changed
Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -18,6 +18,7 @@ commands = pre-commit run --all-files | |||
| 18 | 18 | description = Typecheck with mypy | |
| 19 | 19 | basepython = py39 | |
| 20 | 20 | commands = mypy -p git | |
| 21 | + ignore_outcome = true | ||
| 21 | 22 | ||
| 22 | 23 | [testenv:black] | |
| 23 | 24 | description = Check style with black | |
0 commit comments