Memorisely
Design Engineering

GitHub basics every designer should know

Repos, branches and pull requests without the fear.

Zander Whitehurst

10 min read

GitHub has a reputation among designers as the place where engineers go to speak a secret language. Repos, branches, merges, rebases. It sounds like a lot, and the interface does not exactly go out of its way to welcome you.

The truth is that you only need a handful of ideas to work comfortably with your team. Once those click, GitHub stops being scary and starts being one of the most useful tools you have. Here are the basics, explained the way I wish they had been explained to me.

Git and GitHub are different things

This confused me for an embarrassingly long time. Git is the tool that tracks changes to files on your computer. GitHub is a website where teams store those projects and collaborate on them.

Think of Git as version history in Figma, and GitHub as the shared team space where everyone's files live. You use Git locally, and GitHub is where the work meets everyone else's.

Repositories are just project folders

A repository, or repo, is a project folder with its full history attached. Every file, every change and every comment about those changes lives inside it.

When someone says "clone the repo", they mean download a copy of that project to your computer so you can work on it:

git clone https://github.com/your-team/your-project.git

If you are using an AI coding tool, you can also just ask it to clone the project for you.

Commits are saved checkpoints

A commit is a snapshot of your work at a moment in time, with a short message describing what changed. It is the equivalent of saving a named version.

git add .
git commit -m "Increase padding on pricing cards"

Good commit messages describe the change, not your mood. I have a repo from my early days with commits called "fix", "fix again" and "please work". Future me was not grateful.

Branches are safe places to experiment

A branch is a separate copy of the project where you can make changes without affecting anyone else. The main branch, usually called main, is the version that goes live.

Before you start any work, create a new branch:

git checkout -b update-pricing-cards

It is a lot like duplicating a Figma page to try an idea. If it works, you bring it back. If it does not, you throw it away and nobody is any the wiser.

Most Git ideas map neatly onto things designers already do in Figma.

Pushing and pulling

Your commits live on your computer until you push them to GitHub. Pushing uploads your branch so others can see it:

git push

Pulling does the opposite. It downloads the latest changes from your team so your copy stays up to date:

git pull

A good habit is to pull before you start work each day. It saves you from building on top of an old version of the project.

Pull requests are design reviews for code

A pull request, or PR, is a request to merge your branch into main. It shows exactly what changed, line by line, and gives your team a place to comment and approve.

If you have ever shared a Figma link and asked for feedback, you already understand pull requests. The only difference is that the thing being reviewed is code. A good PR includes:

  • A clear title describing the change
  • A short explanation of why
  • Before and after screenshots, which engineers love from designers
A clear title, a short why and screenshots give reviewers everything they need.

Reading a diff

When you open a pull request you will see a diff. Lines in red were removed, lines in green were added. That is it.

You do not need to understand every line to review a diff. Look for the bits you do recognise, like copy, colours and spacing values. Over time more of it starts to make sense.

When things go wrong

Two things scare designers most: merge conflicts and breaking main. Both are less dramatic than they sound.

A merge conflict just means two people changed the same line and Git needs a human to choose. Your AI tool can usually explain and resolve it with you. Breaking main is rare if you always work on a branch and get a review first, and even then every commit can be undone.

The first time I hit a merge conflict, I assumed I had corrupted the entire project and messaged an engineer in a mild panic. He fixed it in about fifteen seconds and kindly pretended it was a tricky one.

Start with one repo

Ask your team for access to your product's repository. Clone it, create a branch and change one small piece of copy. Commit it with a clear message, push it and open a pull request with a screenshot. You do not have to merge it. Just going through the steps once takes most of the fear away.

Going through every step once, on something tiny, is the fastest way past the fear.

We cover Git and shipping code properly in our AI Design Engineering Bootcamp.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all