Stage 6 · Lesson 7 of 7
Publishing on GitHub
Publishing is the last step of the project, not an afterthought. The needs a clear name, a one-line description and the README. It also needs a file, which tells others what they may do with your code ( is a common default for small projects).
Add a .gitignore, and check that no secrets or generated files are committed. The commit history should tell the story honestly. Aim for small commits with that say why, not one "final" commit containing everything.
Add topics (tags on ) so people can find it, and pin your best two projects on your GitHub profile. Once it works, tag a first release, such as v1.0.0. The point is simple: anyone can open the repository and see finished, tested work that is clearly yours.
A question to check yourself, an AI practice session and 2 cheat sheet entries come when you add the roadmap to your account. Add it
Resources for this stage
Start with
- GitHub repoFreeProject Based Learning
Community maintained · Beginner
Follow one guided build in your language, then build your own without a guide
Keep handy
Also worth your time
How to present each project: the problem, stack, challenges and results
- Build Your Own XGo deeper
When you want a harder build: a shell, a key-value store or a tiny Git, from scratch