Also, put in a readme, that makes it easier for me to evaluate the project. And put in tests, so I know you are familiar with those. In short, show me you know what you are doing by actually doing it.
Committing to build and grow a github is probably the single best thing a developer without a degree can do.
Or even a dev with a degree.
I've gotten a number of interviews based on my github and projects, without even sending a resume. For all the interviewer knows, I never went to school. And when I hire, I look at github first, maybe a resume if there isn't a github. Or, equally likely, no github -> resume goes into the circular file.
Test coverage is nice to have, but I don't know that it's a requirement up front. I can't think of any circumstances where having test coverage will hurt, so I'd agree that it should probably be there, even if you're not a TDD/BDD zealot. It at least shows that you're familiar with testing and can do it.
Having a github account with several projects on it is a big positive signal. There will be companies who feel that you need a degree, but that's a small portion of the job market. Committing to build and grow a github is probably the single best thing a developer without a degree can do.