Proof beats claims
Your repo is your proof. A recruiter or hackathon reviewer should open it and see what data you used, how you split it, what model you trained, and what result you got.
Do not just upload a notebook called final.ipynb. Ship a small project that runs from clean steps.
What your repo needs
Keep it boring and clear. A simple scikit-learn model with honest evaluation is better than a messy deep learning repo that nobody can run.
Your repo must answer five questions: Where is the dataset from? What is the target? How did you split train and test? Which model did you choose? What metric did it score on test data?