If you don’t have style rules baked into the PR process, you should. Tabs vs. spaces is a team decision and needs to be matched by everyone to reduce code churn. It’s correct to reject a PR if it violates the team style guide (although it should be automated and have tooling locally to enforce it as well.)
the only thing that matters is making money fast. everything else DOES NOT MATTER, and ESPECIALLY not the invisible characters between the words.
I worked for twitter and there was a guy like this. I made a big stink that "yo, everything this guy says just needs to be in a linter" and they actually implemented it.
On the contrary, the pro is likely to prefer tabs—you can adjust the display-width for better ergonomics.