A B has a GitHub as a résumé question

Hi Chris and Mike. Love the show.

I've been programming as a hobby for several years, and it's high time for me to turn it into a job™.
I have no degree (university and I didn't get along very well), and no working experience. So, as I see it, my only real way to prove my ability to potential employers is through GitHub.

I took a crack at actually finishing and publishing a project of mine for the first time. I made a medium-sized program in Python with Qt framework. It got a couple hundred stars on GitHub upon release (it's my only real "success" metric) and I'm pretty satisfied with the whole endeavor.

The question is how many of these projects do I need to confidently put a GitHub profile link as my "résumé" for the lowliest developer position? What do employers even look for in a résumé like that? What would be red flags or instant deal breakers? (I currently have no docs or tests, so that's probably one of them)

Cheers, keep up the great show.