Yet there are otherwise, like clang auto formatter. Instead of using right away. We may need to discuss and agree as a community which tool we will use.

And also which settings will be used, ideally be stored into the git repo (root folder), which then get picked up by the relevant tool.

In fact, I'm would like to go to next level, namely automated CI/CD. Which may include auto-formatter, other tools maybe like static code analysis (cppcheck), generation of documentation (from source code) and running testcases within a pipeline.

Read my message #62 on bug report: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1469#62

Ps. Where are the testcases? We may need to start creating (integration/unit) testcases to avoid regression issues when changing code.