Git & GitHub
Your GitHub repo is the proof that your project exists, runs, and was built by your team. Before you submit, check it from a stranger’s view, not from your laptop.
A recruiter or judge should understand what it does, how to run it, and what changed over time without messaging you.
0 of 8 lessons done · proved by a submitted project with a public repository
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
A common mistake is submitting a local folder path, a Google Drive zip, or a link that only works for your account. HackIndia needs a public GitHub repository link.
Another mistake is pushing code but forgetting environment instructions. If your project needs API keys, say which variables are needed, but never commit the real keys.
Run these commands in your project folder before submission. They help you catch uncommitted work and confirm your code is connected to GitHub.
git status
git log --oneline -5
git remote -v
git branch --show-currentgit status should say your working tree is clean. If it shows modified files, either commit them or remove the changes if they are not needed.
git log should show recent commits with useful messages. git remote -v should show the GitHub URL you plan to submit. Your current branch should be the branch visible on GitHub, usually main.
You can ask ChatGPT, Gemini, or Claude to review your README before submission. Paste the README and ask: “Can a first-year student run this project from these instructions? List missing steps only.”
Check every suggestion. AI may assume commands, package managers, ports, or file names that your repo does not use.
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Answer the quick check to finish this lesson.