Setting up Git and Initializing Repositories¶

A guide to getting started with Git, from installation to creating your first repository.

Installing Git¶

Windows¶

Official Installer¶

Download from https://git-scm.com/download/win and run the installer with default options.

Using Winget¶

winget install --id Git.Git

Using Chocolatey¶

choco install git

macOS¶

Using Homebrew¶

brew install git

Using the official installer¶

Download from https://git-scm.com/download/mac and follow installation instructions.

Linux¶

Debian/Ubuntu¶

sudo apt-get update

sudo apt-get install git

Fedora¶

sudo dnf install git

RHEL/CentOS¶

sudo yum install git

Arch Linux¶

sudo pacman -S git

Verify installation¶

git --version

Initial Configuration¶

Setting Your Identity¶

Git requires knowing who you are for commit attribution:

Set your name¶

git config --global user.name "Your Name"

Set your email¶

git config --global user.email "[email protected]"

💡 Tip: Use the same email address you use for your remote Git hosting service (GitHub, GitLab, etc.).

Configuring Your Editor¶

Set your preferred text editor for commit messages:

For VS Code¶

git config --global core.editor "code --wait"

For Vim¶

git config --global core.editor "vim"

For Notepad++ (Windows)¶

git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"

For Sublime Text¶

git config --global core.editor "'subl' -w"

Checking Your Settings¶

Review all your settings:

List all settings¶

git config --list

Check a specific setting¶

git config user.name

git config user.email

Configuration Levels¶

Git configurations can be applied at three levels:

System level¶

Applies to all users:

git config --system ...

Global level¶

Applies to all repositories of current user:

git config --global ...

Local level¶

Applies only to current repository:

git config --local ...

📌 Note: Local settings override global settings, which override system settings.

Creating Repositories¶

Initializing a New Repository¶

Turn an existing directory into a Git repository:

Navigate to your project directory¶

cd path/to/your/project

Initialize the repository¶

git init

After initializing, you'll see a .git directory which contains all the Git metadata.

Cloning an Existing Repository¶

Copy a repository from a remote server:

Clone via HTTPS¶

git clone https://github.com/username/repository.git

Clone via SSH¶

Requires setup of SSH keys:

git clone [email protected]:username/repository.git

Clone to a specific directory¶

git clone https://github.com/username/repository.git my-project

Clone a specific branch¶

git clone -b branch-name https://github.com/username/repository.git

Clone with limited history¶

Shallow clone:

git clone --depth=1 https://github.com/username/repository.git

Understanding the .git Directory¶

The .git directory contains all the data and configuration for your repository:

.git/
├── HEAD          # Points to the current branch
├── config        # Repository-specific configuration
├── description   # Description of the repository (only used by GitWeb)
├── hooks/        # Client or server-side hook scripts
├── index         # Staging area information
├── objects/      # Git's object database (commits, trees, blobs)
└── refs/         # Pointers to commit objects (branches, tags)

⚠️ Warning: Never manually modify files in the .git directory unless you know what you're doing.

First-time Repository Setup¶

Standard Project Files¶

When creating a new repository, consider adding these standard files:

Create a README file¶

echo "# Project Name" > README.md

Create a license file¶

Example: MIT

curl -o LICENSE https://opensource.org/licenses/MIT

Create a .gitignore file¶

Discussed below:

touch .gitignore

Creating a .gitignore File¶

The .gitignore file specifies intentionally untracked files that Git should ignore:

touch .gitignore

Sample .gitignore content for various project types:

Node.js¶

node_modules/
npm-debug.log
.env

Python¶

__pycache__/
*.py[cod]
*$py.class
venv/
.env

Java¶

*.class
*.jar
target/
.idea/

💡 Tip: Use gitignore.io to generate .gitignore files for your specific tech stack.

Command Summary¶

Related Topics¶

• Basic Git Usage
• Branch Management
• Remote Operations
• Merging and Rebasing
• Stash and Clean