It goes hand in hand with the industry shift (especially for frontend tech) with considering one's GH as an essential aspect of one's resume. I wonder how much

It goes hand in hand with the industry shift (especially for frontend tech) with considering one's GH as an essential aspect of one's resume. I wonder how much of that shift is also just perception within a certain bubble/echo chamber, though. There's certainly a trend in online forums and startups to ask applicants for their GH profile, but I suspect this is one of those things that some employers are doing because they think everyone else is. Are those employers really then reviewing all of those profiles to see which include projects where an applicant really made a meaningful contribution and which are just token updates or yet another ad hoc, informally-specified, bug-ridden, slow implementation of half of someone else's popular and established work? The only thing I know for sure about that sort of policy is that it would immediately rule out most of the best developers I've ever worked with. Most of those people are busy building working projects for their businesses/clients/employers during work hours, and then having a life at other times. Some do contribute back to OSS projects or help answering questions on online forums as well, but not as a resume-building exercise, and it's rarely where you'll find the best indications of what they are capable of building.