Now that you know how most code professionals use GitHub, you probably realize that people are going to look at your GitHub repos when they are thinking about whether to hire you or offer you an internship.
Here’s how to make any GitHub repo more professional:
- Add a .gitignore file. This prevents unnecessary files from being uploaded to GitHub, even though you keep those files in the repo folder on your computer. Read how to make one.
- Add a LICENSE file. This specifies how (or if) people can use your files. It’s easy to create one. Without a license in your repo, your files are not truly open source!
- Add a requirements.txt file. This lets people easily download all the dependencies needed to run your code. This file is very simple to create and to use.
- Add a description, a link to live pages (maybe on github.io) and topics.
- Write and add a proper README.md file. Use GitHub’s flavor of Markdown (slight differences from generic Markdown). This is super easy. The purpose of the README is to explain what’s in your repo, what it does, and how to use it. Make sure to use headings intelligently — it makes the document so much more readable.
- Last but far from least, name your repo appropriately. Short and descriptive is the way to go. Notice that most repo names are all lowercase, with hyphens. The repo name is the same as the folder name on your computer. (If you rename an existing repo on GitHub, your GitHub Desktop app will certainly get confused!)