Git Setup: Your First 10 Minutes After Installation

Configure Your Git Identity

You've installed Git. Congratulations. The next hurdle isn't complex; it's just knowing what to type. Every developer eventually faces this. The crucial first step is telling Git who you are. Each commit you make permanently records your name and email. Git needs this information to attribute your work. Without it, Git refuses to commit anything.

Here are the commands, which work across Windows (Git Bash), macOS Terminal, and Linux shells. These settings are global, meaning they apply to all your Git projects on this machine.

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Replace "Your Name" with your actual name and "you@example.com" with your email address. This email doesn't need to be public; it's for attribution within your repositories.

Next, set your default branch name. While main is now the industry standard, older Git versions default to master. To ensure consistency and avoid confusion, set your default branch to main:

git config --global init.defaultBranch main

These commands establish your identity. Think of it like setting up your signature on every document you'll ever create. Git needs this permanent record.

Initialize Your First Repository

With your identity set, you're ready to start a new project or begin tracking an existing one. This involves initializing a Git repository. A repository, or 'repo', is simply a project's folder that Git will manage.

Navigate to your project's root directory using your terminal. If you don't have a project yet, create a new directory and then navigate into it.

mkdir my-new-project
cd my-new-project

Once inside your project directory, initialize Git:

git init

This command creates a hidden .git sub-directory within your project. This directory contains all the necessary Git metadata for your repository. You won't typically interact with it directly, but it's the heart of your Git-managed project.

After running git init, Git is now tracking this directory. However, it's not yet tracking any files within it. You need to tell Git which files to track.

Stage and Commit Your Initial Files

Git operates on a two-stage system: the staging area and the repository itself. The staging area is an intermediate space where you prepare files for your next commit. This allows you to carefully select exactly what changes go into each commit.

Let's create a simple file in your project directory. For example, a README file:

echo "# My New Project" > README.md

Now, check the status of your repository. This command shows you which files are untracked, modified, or staged.

git status

You'll see README.md listed under 'Untracked files'. To include this file in your next commit, you need to add it to the staging area:

git add README.md

Run git status again. You'll now see README.md under 'Changes to be committed'. This means it's staged and ready.

The final step in this initial sequence is to commit the staged changes. A commit is a snapshot of your project at a specific point in time. Each commit needs a message describing the changes made. This message is crucial for understanding the project's history.

git commit -m "Initial commit: Add README.md"

The -m flag allows you to provide the commit message directly on the command line. The message "Initial commit: Add README.md" clearly states what this commit does.

After this commit, git status will report that your branch is up to date with no changes to commit. You have successfully initialized a Git repository, added a file, and made your first commit. These ten minutes of configuration lay the groundwork for all future version control activities.

What nobody has addressed yet is how many developers bypass these initial steps, leading to inconsistent commit histories and confusion when collaborating. Treating these first ten minutes as a mandatory onboarding process for every new Git user could prevent significant downstream issues.