From 91085df702455e9a9629a4fc7c70c3ad8e6722d8 Mon Sep 17 00:00:00 2001
From: Eric Harney <eharney@redhat.com>
Date: Wed, 27 Apr 2022 12:35:08 -0400
Subject: [PATCH] Run pylint tox env on all files by default

The pylint tox env and job currently only run
on the files changed in HEAD.  This is confusing,
because changes regularly merge which introduce new
pylint errors, which will not show up in a pylint
run until another patch touches that file.

Instead, just run pylint on all of Cinder to get
consistent output.

Depends-On: Icb4c0b5cbba02c42e9e2ee381dc9152f1c1de22c
Depends-On: I3e17c6a2a7f252a9d324a1fea616e22869e55702
Change-Id: I98fd7f76e5d3d096970d6c5f1652e9ee2abeebd6
---
 tox.ini | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tox.ini b/tox.ini
index 22f5401d24e..2bea98e7e5d 100644
--- a/tox.ini
+++ b/tox.ini
@@ -95,7 +95,7 @@ deps = -r{toxinidir}/requirements.txt
        -r{toxinidir}/test-requirements.txt
        pylint==2.11.1
 commands =
-  {toxinidir}/tools/coding-checks.sh --pylint {posargs}
+  {toxinidir}/tools/coding-checks.sh --pylint {posargs:all}
 
 [testenv:cover]
 # Also do not run test_coverage_ext tests while gathering coverage as those