What your profile README actually does
Your GitHub profile README is the first thing a stranger sees.
One question trips up almost everyone who writes one: should you feature finished projects, or is it okay to show work in progress?
The honest answer is that both can work, but they do different jobs.
This guide walks through what each choice signals, when to use it, and how to describe unfinished work without making it look abandoned.
GitHub lets you create a profile README that appears at the top of your profile page.
You decide what goes in it, so you have full control over how you present yourself.
Common sections include an about-me blurb, contributions you are proud of with context, and guidance for getting help in communities where you are involved.
You can format all of it with GitHub Flavored Markdown, including emoji, images, and GIFs. GitHub's profile documentation describes these options in detail.
That control is the whole point.
Your README is not an automatic feed of everything you have done.
It is a curated front page, which means every item you add is a claim about what you want to be known for.
Alongside the README, you can pin up to six public repositories or gists to your profile.
Pinned items sit near the top and show key details, working with your README as a single first impression.
GitHub's pinning guide covers how to choose and reorder them.
What finished projects signal
A finished project is a complete claim.
It says: I set out to build something, I finished it, and here is the result.
For collaborators, clients, and hiring managers, that completeness matters because it reduces uncertainty.
They can look at the code, run it, and judge the outcome without wondering whether the hard parts were ever done.
Finished work is also easier to describe.
You can state what the project does, what problem it solves, and what you learned, all in the past tense.