GitHub Profile Checklist for Developers

What this checklist is

A 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.

It has 7 chapters and 30 checks, each with how to verify it and how much it matters. For developers, students and fresh graduates.

Chapter by chapter

1. Name, photo, bio and links (5 checks)

The top of your profile tells a visitor who you are and where else to find you. Fill in the fields GitHub gives you.

2. Profile README (4 checks)

A profile README is the free-form section at the top of your profile. Make sure it actually appears, then keep it short and specific.

3. Pinned repositories (4 checks)

Pins are the only part of the profile you fully curate. Use them for the work you most want people to open.

4. READMEs for the projects you show (4 checks)

A pinned repository with no README is a dead end. Each project you show should explain itself and be runnable by a stranger.

5. Licences, secrets and repository hygiene (5 checks)

Small signals that show you build software the way teams do: a licence, no committed secrets, sensible ignores, tests and clear history.

6. Contribution graph and commit email (5 checks)

Why your work does or does not show on your graph, and how to get credit without exposing your personal email.

7. Account security (3 checks)

Your GitHub account can push code and publish packages. Protect it like a bank account.

How it works on Sefism

The checklist is one page: each check has a severity (must, should or nice to have) and a concrete way to verify it, and members can tick checks off as they go. The opening chapters are open to everyone. Adding it to your account uses credits, opens every chapter and keeps your progress.

Every claim is checked against the sources listed on the page (8 cited).