From 12cf909acde3241abfc5b5eee99b2d79e296eedf Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Fri, 24 Apr 2026 15:38:55 +0200 Subject: [PATCH] docs: clean linting part of contributing guide of yamllint The development flow guide mentioned several tools that needed to be installed in the PATH to run make lint. This change removes yamllint from that list now that makeyamllint has been made self-contained. With pylint the only remaining requirement, this also rewords the corresponding section for clarity. Signed-off-by: Michael Adam --- Documentation/Contributing/development-flow.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/Contributing/development-flow.md b/Documentation/Contributing/development-flow.md index 03a61d5a8..679fd24dc 100644 --- a/Documentation/Contributing/development-flow.md +++ b/Documentation/Contributing/development-flow.md @@ -256,13 +256,13 @@ Common cases that may need tests: ## Linting -Run `make lint` to run all linters. This will require the following CLI tools to be installed on the system: +Run `make lint` to run several linters. This will require +the [pylint](https://www.pylint.org/) CLI tool to be installed on the system in the PATH -* [yamllint](https://www.yamllint.com/) -* [pylint](https://www.pylint.org/) - -Many of those tools are available via `brew` for MacOS or as Linux distribution packages. -Otherwise refer to the respective project websites for installation instructions. +pylint is available via `brew` for MacOS and as a distribution package +for many Linux distributions. It can also be installed into the system +or a python virtual environment (venv) with `pip`. +Refer to the respective project website for more installation instructions. !!! tip Run `make help` to see a list of all possible make targets