Portfolio Toolkit

Set up GitHub so your code speaks for you

8 minutesLast verified July 2026Free

I

Why it matters

For technical roles, this matters more than almost anything else in your application — a hiring manager who wants real evidence of how you build will look here before anywhere else. GitHub isn't a resume line; it's a place someone can actually read your code, see how you think, and watch a project come together over time.

You don't need a large or polished body of work. A few real projects, described honestly and kept tidy, tell a truer story than a long list of half-finished ones.

II

Create your account

  1. 1Go to github.com and sign up with a personal email you check regularly.
  2. 2Choose a username you'd be comfortable putting on a resume — your real name or a close, professional variant of it.
  3. 3Add a profile photo and a one-line bio naming what you're working toward.
  4. 4Create a repository named exactly after your username to unlock a profile README, which renders on your main profile page.
  5. 5Turn on two-factor authentication (2FA) while you're in account settings.
III

Set it up right

  • Profile README: a short welcome — who you are, what you're learning, and what you're currently building.
  • Pinned repositories: choose your three or four strongest projects to pin to the top of your profile, so a visitor sees your best work first.
  • Per-project README: for each pinned project, explain what it does, how to run it, and what you learned building it.
  • Commit history: commit as you go rather than in one final upload — a history of real, incremental work is itself evidence.
  • Project variety: if you can, pin a mix that shows different skills rather than four versions of the same idea.

A short, clear README on a small project usually reads better than a long, undocumented one on a large project. Explain the “why,” not just the code.

IV

Best practices

  • Write commit messages that describe what changed and why, not just “update” or “fix.”
  • Keep working on at least one project over time — recent, ongoing activity says more than a single old burst of commits.
  • Remove or archive early practice projects that no longer represent your current skill, so your pinned work stays your strongest work.
  • Use descriptive repository names instead of generic ones like “project1.”
  • Link your GitHub profile from your resume and any other profile you keep, so all your threads point to each other.
V

Mistakes to avoid

  • A repository with code but no README — the same project, explained, is worth far more than the project alone.
  • Committing an entire project in one dump right before an application, with no history behind it.
  • Pinning old or abandoned work instead of your current strongest projects — take a minute to update your pins as your skills grow.
  • A username or profile photo that reads as unfinished or informal for a professional audience.

All toolkit guides

Set up GitHub so your code speaks for you · Knock