Checklist · Career
GitHub Profile Checklist for Developers
Opens with creditsA part-by-part GitHub profile checklist for developers and CS students. It covers the profile basics, a profile README that earns its space, choosing and presenting pinned repositories, READMEs that let a stranger run your project, licences and repository hygiene, why contributions do or do not appear on your graph, keeping your email private, and securing the account.
Written by Tauseef Fayyaz7 chapters, 30 checksAbout 19 minReviewed 13 October 2026What you will learn
7 chapters · about 19 min
1Name, photo, bio and linksThe top of your profile tells a visitor who you are and where else to find you. Fill in the fields GitHub gives you.5 checks · 3 min
- 1Use a username you are happy to put on a CV and in a URL
- 2Add your name and a clear profile picture
- 3Write a bio that says what you build, within 160 characters
- 4Add your website, up to four social accounts and a location
- 5Use the status message only when it tells people something useful
5 in this chapterOpen this chapter2Profile READMEA profile README is the free-form section at the top of your profile. Make sure it actually appears, then keep it short and specific.4 checks · 3 min
- Pinned repositoriesPins are the only part of the profile you fully curate. Use them for the work you most want people to open.4 checks · 3 minOpens with credits
- READMEs for the projects you showA pinned repository with no README is a dead end. Each project you show should explain itself and be runnable by a stranger.4 checks · 2 minOpens with credits
- Licences, secrets and repository hygieneSmall signals that show you build software the way teams do: a licence, no committed secrets, sensible ignores, tests and clear history.5 checks · 3 minOpens with credits
- Contribution graph and commit emailWhy your work does or does not show on your graph, and how to get credit without exposing your personal email.5 checks · 3 minOpens with credits
- Account securityYour GitHub account can push code and publish packages. Protect it like a bank account.3 checks · 2 minOpens with credits
About this checklist
A GitHub profile checklist is useful because your GitHub page is often the first place someone looks at your actual code. A hiring engineer, an open source maintainer or a potential client clicks your link and decides in a minute whether to dig deeper. Most profiles lose them in the same places: no photo or bio, six forks of tutorials pinned at the top, repositories with no README, and a contribution graph that looks empty because commits were made with the wrong email.
This checklist walks through your GitHub profile in the order a visitor sees it. It starts with the basics (name, photo, bio and links), then the profile README and pinned repositories. The middle chapters cover the READMEs, licences and hygiene of the repositories you show off. The last chapters explain how the contribution graph really counts your work, how to keep your personal email out of public commits, and how to secure the account itself.
Every item says what to do and how to check it. Feature names and limits were checked against GitHub's own documentation in October 2026. GitHub moves settings around from time to time, so if a menu has changed, search GitHub Docs for the feature name used here.
The goal is not a flashy profile. It is an honest one where your best work is easy to find, easy to run and clearly yours, whether you are a student building your first portfolio or an experienced engineer whose work is mostly in private repositories.
Common questions
How do I add a README to my GitHub profile?
Create a public repository with exactly the same name as your username and add a README.md file with content in its root. GitHub shows it at the top of your profile automatically. If the repository existed before July 2020, use Share to profile in the repository.
Why are my commits not showing on my GitHub contribution graph?
The most common reasons are that the commit email is not linked to your account, the commits are on a branch other than the default branch, or they were made in a fork. Check the email in the commit's .patch view, merge the work into the default branch, and allow up to 24 hours for the graph to update.
How many repositories can I pin on GitHub?
You can pin up to six repositories and gists combined. Choose original, working projects with a clear README, put the most relevant one first, and give each a one-line description.
How do I hide my email address on GitHub commits?
Turn on Keep my email addresses private in your GitHub email settings, then set your Git user.email to the GitHub-provided noreply address shown there. New commits will use that address and still count on your graph. Commits you already pushed keep the old email.
Should I add a licence to my portfolio projects?
If you want others to use or learn from your code, yes. GitHub explains that without a licence default copyright laws apply and others may not copy, distribute or create derivative works. Do not add a licence to code you do not own, such as client work.
What should a student put on a GitHub profile with few projects?
Pin your two or three best projects with clear READMEs, setup steps and a screenshot, add a short bio and profile README, and start contributing to an open source project you use. A few well-presented projects are better than many empty ones.
Sources (8)
Checked against these, last on 13 October 2026.
- Managing your profile README, GitHub Docsdocs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
- Personalizing your profile, GitHub Docsdocs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile
- Pinning items to your profile, GitHub Docsdocs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile
- Classifying your repository with topics, GitHub Docsdocs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics
- About the repository README file, GitHub Docsdocs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
- Licensing a repository, GitHub Docsdocs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
- Why are my contributions not showing up on my profile?, GitHub Docsdocs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
- About mandatory two-factor authentication, GitHub Docsdocs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/about-mandatory-two-factor-authentication
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allCheat sheets
See allBest practices
See all- Personal Branding Best Practices for DevelopersPersonal branding for developers without the hype: pick a focus, keep one consistent presence, show proof of work, learn in public, engage well and build a reputation that lasts.
- Content Creation Best Practices for DevelopersHow developers create useful public content: blog posts, newsletters, LinkedIn and X posts, YouTube and Shorts, choosing formats, staying consistent, repurposing, measuring and using AI honestly.
Checklists
See all- LinkedIn Profile Checklist for DevelopersCheck your LinkedIn profile section by section: photo, headline, About, Experience, Featured, Skills, custom URL, Open to Work, posting and privacy.
- Developer Portfolio Website ChecklistCheck your developer portfolio site end to end: clear intro, 3 to 5 strong projects, live demos and code, speed, accessibility, SEO basics, custom domain, contact, analytics and upkeep.
- Freelance Platform Profile ChecklistBuild a freelance profile that wins work on Upwork, Fiverr, Toptal or Contra: niche, title, overview, portfolio, rates, first jobs, proposals, reviews, and each platform's rules and fees.
Career questions
See all- What does proof of work mean for a fresher developer?Proof of work is evidence someone can check in a few minutes that you can do the job: a deployed project real people could use, readable code with tests, a pull request merged into someone else's project, or a clear write-up of a problem you solved. It replaces the experience a fresher does not have yet, so it must be easy to find and easy to verify.
- Everyone around me has internships, GitHub projects and achievements, and I have almost nothing. What should I do?Stop comparing your starting point with other people's highlights and start producing evidence of your own. In the next three months you can build one solid project, one smaller one, a clean GitHub and LinkedIn, and a targeted internship pipeline. That is enough to change your position.
- What projects should I build in my first year of university?Build small, finished projects that solve problems you or people around you actually have: a script that automates a chore, a command line tool, a simple website for a society or family business. First year is about finishing things and using Git, not about impressive ideas.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com