I try to do the same, however it is an up hill battle with HR if the github contents happen to be in distinct domains that what the CV states.

The problem there is not with your Github contents. The problem is with the kind of HR staff who are not technically knowledgeable enough [1] to understand that skills in other domains can translate to skills in the needed domains. Should consider looking for jobs where the technical leadership do the hiring or at least have a large say in it, as in, they are the ones who vet you technically, not the HR. Many HR people just use a buzzword match (Java 5 years exp? no? out!) and reject blindly based on that. (Cue HR jokes like them putting out job descs. for 6 year of Rails exp. when Rails was 2 years old - substitute any other tech too, same story.) HR should only be involved for talks like starting date, perks, joining docs, etc. There are jobs or contracting roles like that, mainly with startups, and I have gotten such gigs. Even in some large enterprise companies where I worked earlier, the technical and managerial parts of the interviews were mostly done by the tech leader or tech managers in the company. I've been interviewed by tech leaders even when I was a junior dev. And that is not uncommon. All depends on the kind of company you apply to.

[1] And this is why the "hiring is broken" topic comes up often on HN and other forums, because it is so. Even management, many times, have a shortsighted and wrong view towards what hiring (and related stuff, like what you do after you join) is (or should be) all about.

Edited for grammar and to add stuff.