summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlouiz’ <louiz@louiz.org>2018-10-18 21:32:51 +0200
committerlouiz’ <louiz@louiz.org>2018-10-18 21:32:51 +0200
commit08d31d4fc74913a7f6998bfda0de9da2d8d05bbd (patch)
tree3dd19ba394968b7ff826d350b5739b14d06791d4
parent9b95b65addf1e543309850d37207a01990cb469f (diff)
downloadpoezio-08d31d4fc74913a7f6998bfda0de9da2d8d05bbd.tar.gz
poezio-08d31d4fc74913a7f6998bfda0de9da2d8d05bbd.tar.bz2
poezio-08d31d4fc74913a7f6998bfda0de9da2d8d05bbd.tar.xz
poezio-08d31d4fc74913a7f6998bfda0de9da2d8d05bbd.zip
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
-rw-r--r--.gitlab-ci.yml9
1 files changed, 0 insertions, 9 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index f1f09443..93129d0d 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -86,12 +86,3 @@ pylint-plugins:
- pip3 install -r requirements-plugins.txt
- python3 setup.py install
- 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'"