That's a myth. Google's performance reviews, as flawed as they are, still require one to provide references to deliverables like reviewed commit history and reviewed documents written. Doing no work will result in poor performance ratings after a couple review cycles, since you will have no deliverables to your name. Those who produce nothing at all are routinely put on performance plans and then fired if things don't change. I've seen that happen.

That said, the Google performance review system, at least in my experience, can favor those who are strategic about choosing and promoting their work even if it is lower in quantity, and disadvantage those who do the a lot of work but aren't strategic about choosing and promotion it. That's almost by design, since in theory Google favors "impact" over lines of code.