In all three cases, I eventually trained everyone how to use git, so there is that as well.
as opposed to a non-working repo? do you mean the code in it "worked" or just that you had repos up?
ANECDOTE TIME: I knew of a guy who was hired because his github profile page showed a lot of stars. It didn't dawn on them until after he was hired that those are things that he starred, not stars received for his projects. He had "a lot of repos". Cursory inspection showed all but 2 (of the 40+) were forked. He was a horrible hire, and left after a few months, but the dept manager who'd hired him (against input from some of the team) got uber-defensive about any criticism (this person was in way over their head from a tech and management standpoint) and... multiple people (surprisingly, anyone who'd made any criticism of the 'mr github stars' profile) ended up getting 'reduced' (laid off) a couple months later.
You don't have to have a huge contribution history or a project with a ton of stars, just having something out there matters to some places.
> GitHub has a rich ecosystem of free tools for building, packaging, testing and much more. All these tools are mandatory for professional software development.