We still have 79 bashate warnings for lines longer than 79 characters.
bashate also warns about here documents, so cutting down on all of
them is not worth it. Let's disable these bashate warnings so that we can
see the real problems.
Warnings disabled are of the form:
[W] E006: Line too long: ...
Change-Id: I3abfae4432f9432af6e0d8b43bfc340673f06802
Like pep8 before we are trying to reduce the amount of jobs launched
in the check / gate pipelines. Over the last 200 commits only 2 or 3
files have been touched.
We are also reducing run-bashate.sh and remove unsourced files.
Change-Id: Ie77fad9a272fb41fbb48f94ceee910954e903939
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
My repository contained .test directory from different tests and
that failed the bashate test, exclude it from bashate checks so
that tox -e bashate works locally.
Change-Id: I99c531d425cfc4464ec7461b339fd0b40ce13148
Also create tools/run-bashate.sh to wrap a find command to search for
files to run bashate on, and use it in tox.
Change-Id: I5ab07425f566a556f158a4b76b00aa35f9fb4385
