No, all it shows is that they wrote some code and put it on a website.
The developer that has just a resume might be just as (or more) skilled that the one that uses github but for whatever reason can't post code up like that. To exclude someone simply because they don't have an active github is foolish.
However did you screen, interview, and hire people before github came along?
Even if you cannot post code does not men you cannot watch and clone projects so you can learn and stay aware of trends in the community. It keeps you sharp. And it better than any industry magazine out there.
Rivera finds that interviews are where "fit" is ultimately determined, but résumé screening is a first step: "firms mandated that evaluators assess candidates’ fit along with a variety of technical and communication skills in résumé screens and first- and second-round job interviews" (p. 1007).
And my evidence is personal experience. I do not need a study to know that interacting more with people makes me a better team player. I know that I have benefitted greatly by cutting back on time reading articles and attending meetups and more time with GitHub activities.
The author's work may very well not be worth sharing on GitHub - it may be worth much more than "free".
These days if I interviewed 2 developers and one had a very nice resume full of recommendations and stories about successful projects and the other developer had an active GitHub account with their own active projects with many watching them as well as multiple accepted Pull Requests for other projects... I would easily lean toward the developer who has been actively writing code, sharing and interacting with other developers. It shows they have passion, drive, dedication and an eagerness to learn from others and contribute back to the community.
A fancy resume cannot replace all of that.