How so? It's on the code review. They see the change, and learn about it..?

99.9% of code review that I do, and that I get, is not training. So maybe don't make all the changes for new employees? I use vim. Most people at my work use vim. Our build process is complex. Everything we do is really complicated. It works for the experienced, yet it has a learning curve.

So, new people get a slightly different experience. That's fine.

You could make the comment about the change, then create a fixup commit and allow the original author to decide to merge it or not.