Remove the formatting-check ci build until we decide what we should do with it
If we ignore it, it’s just noise. We need to decide: - fix the code to be like yapf wants to be (I’m against this) - change the rules, to make them way more flexible, and then apply them - don’t run yapf at all
This commit is contained in:
parent
9b95b65add
commit
08d31d4fc7
1 changed files with 0 additions and 9 deletions
|
@ -86,12 +86,3 @@ pylint-plugins:
|
||||||
- pip3 install -r requirements-plugins.txt
|
- pip3 install -r requirements-plugins.txt
|
||||||
- python3 setup.py install
|
- python3 setup.py install
|
||||||
- pylint -E plugins
|
- pylint -E plugins
|
||||||
|
|
||||||
formatting-check:
|
|
||||||
stage: test
|
|
||||||
image: python:3
|
|
||||||
allow_failure: true
|
|
||||||
script:
|
|
||||||
- pip3 install yapf
|
|
||||||
- yapf -dpr poezio
|
|
||||||
- "[ -n \"$(yapf -dpr poezio)\" ] && echo 'Formatting check failed, please run yapf' && exit 1 || echo 'Formatting check succeeded'"
|
|
||||||
|
|
Loading…
Reference in a new issue