# Pinned Repositories — Resume & GitHub Portfolio

Source: https://www.skillbyai.com/en/resume-portfolio/g-pinned

> Choose what reviewers see first.

## Curate, do not hoard

GitHub lets you **pin** a small number of repositories (and gists) to the top of your profile; at the time of writing the limit is six. Reviewers rarely browse every repository, so pins are your curated shortlist. Pin projects that are **relevant** to the roles you want, **complete enough** to run, have a **good README**, and that you can talk about in depth. Mix in an open source contribution if you have one. Old coursework, forks you never changed and half-finished experiments can stay public, but they should not be pinned. Give each pinned repository a clear one-line description and topics.

## Choosing pins

A simple scoring pass over your repositories.

```text
For each candidate repository, answer yes/no:
  [ ] Relevant to roles I am applying for?
  [ ] Has a README with problem, demo/screenshots and how to run?
  [ ] Runs from a clean clone following the README?
  [ ] Code I wrote myself and can explain line by line?
  [ ] Has tests or CI, or a clear reason it does not?

Pin the repositories with the most "yes" answers.
Do not pin: unchanged forks, tutorial copies, empty repos, abandoned spikes.
Add a one-line description and topics (e.g. spring-boot, postgresql) to each.
```

## A gallery wall

You might own many paintings, but you hang only the few that represent you best at eye level. Pins are your gallery wall.

**Quiz:** Which repository is the weakest candidate for pinning?

- [ ] A small tool you built and use regularly
- [ ] A deployed project with tests and a clear README
- [ ] An open source library you contributed fixes to
- [x] A fork of a popular framework that you never changed

*Answer:* A fork of a popular framework that you never changed. Pins should show your own work.