Git is version control. It tracks changes to files over time, lets multiple people work on the same project without overwriting each other, and makes it possible to undo things that went wrong.
For designers working in code, Git is unavoidable. For designers working with developers who use Git, understanding the basics prevents a specific category of frustrating mistakes.
This is not a complete Git tutorial. It is the minimum that makes you functional.
The Core Concept
A Git repository is a folder that tracks its own history. Every time you make a set of changes and commit them, Git records a snapshot. You can move between snapshots, compare them, and branch off in different directions.
The main branch (usually called main) is the canonical version of the project. You work in branches that are separate from main, and when your work is ready, you merge it in.
Setup
Git — git-scm.com
Download and install Git for your operating system. Verify it is installed by opening a terminal and running git --version.
GitHub Desktop — desktop.github.com
A visual interface for Git. If the command line is unfamiliar, start here. It handles the most common operations with a clear UI and shows you what is about to happen before it happens.
GitHub — github.com
The most widely used platform for hosting Git repositories. Free for public and private repositories. Where most open source projects live.
The Six Commands You Will Use Most
git clone [url] — Downloads a repository from GitHub to your local machine. Start here when you want to work on an existing project.
git status — Shows what has changed since the last commit. Run this constantly. It tells you exactly where you are.
git add . — Stages all changed files for the next commit. The dot means everything. You can also add specific files by name.
git commit -m "description" — Saves a snapshot with a message. Write commit messages that describe what changed and why.
git push — Sends your local commits to GitHub. Run this when you want your work backed up or visible to collaborators.
git pull — Gets the latest changes from GitHub and applies them to your local copy. Run this before you start working each session.
Branches
A branch is a separate line of development. Working in a branch means changes do not affect the main version of the project until you are ready.
git checkout -b branch-name — Creates a new branch and switches to it. Name your branches descriptively.
git checkout main — Switches back to the main branch.
git merge branch-name — Merges a branch into the current branch.
Learning Resources
Git - the simple guide — rogerdudler.github.io/git-guide
The shortest complete introduction to Git that exists. Read this first.
Pro Git — git-scm.com/book
The complete reference. Free online. Use it to look up specific things rather than reading front to back.
Oh My Git! — ohmygit.org
An open source game that teaches Git by visualizing what is happening to the repository as you run commands.
Learn Git Branching — learngitbranching.js.org
Interactive browser-based exercises. The branching and merging sections specifically build the mental model that most written tutorials fail to convey.
The One Habit That Prevents Most Problems
Commit often and with clear messages. Small commits are easier to understand, easier to revert, and easier to explain to a collaborator than large commits that bundle many unrelated changes together.
If you cannot write a clear one-line commit message, the commit probably contains too many things.
Git has a reputation for being intimidating. That reputation is mostly earned in edge cases. In day-to-day use, the six commands above cover the large majority of situations. Start with those and learn the rest when you need it.
Discussion
Loading comments...