Git Get Started

Git Get Started

Initializing a repository creates a hidden .git metadata folder in your project root, turning any local directory into a Git-tracked workspace.

Core Concepts & Explanation

---

Key Steps to Get Started

• Create a project folder
• Navigate to the folder
• Initialize a Git repository

---

Start by creating a new folder for our project:

Example
mkdir myproject
cd myproject

mkdir creates a new directory.

cd changes our working directory.

Now we are in the correct directory and can initialize Git!

Note: Open Git Bash Here (Windows)

If you're using Windows, you can open Git Bash directly in your project folder:

• Right-click the folder in File Explorer
• Select Git Bash Here

This opens a terminal window in the correct location.

---

---

Now that we are in the correct folder, we can initialize Git on that folder:

Example
git init 
Initialized empty Git repository in /Users/user/myproject/.git/

You just created your first Git Repository!

---

What is a Repository?

A Git repository is a folder that Git tracks for changes.

The repository stores all your project's history and versions.

---

What Happens When You Run git init?

Git creates a hidden folder called .git inside your project.

This is where Git stores all the information it needs to track your files and history.

Example: Show Hidden .git Folder (Linux/macOS)
ls -a
.  ..  .git
On Windows, you may need to enable "Show hidden files" in File Explorer to see the .git folder.

---

Troubleshooting

• git: command not found
  Solution: Make sure Git is installed and added to your PATH. Restart your terminal if needed.
• Permission denied
  Solution: Try Practice running your terminal as administrator (Windows) or use sudo (macOS/Linux) if needed.

---

---

Practical Terminal Workflow

Execute the following terminal commands to work with this concept in your workspace:

# Initialize a new Git repository in the current directory
git init

# Inspect the created .git directory
ls -la .git

Best Practices & Pro-Tips

• Atomic Commits: Keep each commit small, focused, and dedicated to a single logical feature or bug fix.
• Imperative Commit Messages: Write commit titles in imperative mood (e.g., Fix CORS bug rather than Fixed CORS bug).
• Review Diff Before Staging: Run git diff to review unstaged modifications before adding files to the index.

Common Gotchas & Troubleshooting

• Detached HEAD State: Triggered when checking out a specific commit hash directly rather than a branch. Create a new branch with git switch -c <branch-name> to preserve edits.
• Accidentally Staged Binary Files: Run git restore --staged <filename> to remove the file from the index without altering your local workspace copy.

Self-Check Challenge

Open your terminal in a test project directory, execute git status, and verify your current working tree state. Practice running git log --oneline to review commit history.