doc: link to code style guide

[refack]

• Subsystem: doc

IMHO we should add a link to the Google Style Guide according to which me are linting C++
and add some Best Practices

After #12540 I thought we should add something like:

---

When editing C++

If you add a new macro or use a new external function, make sure you include the header file explicitly in the file you are editing. This makes sure your change is independent of previous changes, and makes it easier to backport

[gibfahn]

I think in general we try to document our coding style in lint rules. I don't know how easy it would be to lint for this.

[refack]

Yeah I was thinking about that (linting for header include)

[refack]

Still maybe we should have a style-guide to save new devs one "code" -> "lint" -> "fix" cycle

[gibfahn]

Still maybe we should have a style-guide to save new devs one "code" -> "lint" -> "fix" cycle

The problem is that you then have to keep the style guide up to date with the linter. And I'm pretty sure the average dev would rather run the linter for each project than read the style guide, especially when you can just pass --fix to autofix basic issues.

[refack]

So I've been reading cpplint.py, and was reminded nodejs/node-v0.x-archive#8487 that it actualy linting acording to https://google.github.io/styleguide/cppguide.html, so may be a link, and some rules of thumb?

[refack]

Ref: #11753

[Trott]

This should remain open? If so, maybe label help wanted?