Git 102: สร้าง repo และอ่าน statusGit 102: create a repo and read status

The first Git habit is not committing.

The first habit is checking where you are.

git status

git status tells you the state of your working tree and staging area. It is the dashboard.

Check Git is installed

In Terminal or PowerShell:

git --version

If Git is installed, you will see a version number.

If it is not installed yet, install Git using the official installer for your operating system, then come back.

Create a practice folder

Use a folder that contains no private work.

mkdir git-10x-practice
cd git-10x-practice

Now create a small file:

echo "# Git 10x Practice" > README.md

On Windows PowerShell, this command also works.

Initialize the repository

Turn the folder into a Git repository:

git init

Git creates a hidden .git folder. That folder stores repository history and metadata.

Do not edit .git by hand.

Read the first status

Run:

git status

You should see that README.md is untracked.

Untracked means:

This file exists in the folder, but Git has not been told to include it in history yet.

Three common states

You will see these states often.

git status tells you which state each file is in and often suggests the next command.

Add a gitignore early

A .gitignore file tells Git which files should not be tracked.

Create one:

echo ".env" > .gitignore
echo "node_modules/" >> .gitignore

This is not complete for every project, but it shows the idea.

Common things to ignore:

• .env
• dependency folders like node_modules/
• build output
• OS noise files
• logs

If you already committed a secret, .gitignore will not remove it from history. Rotate the secret and ask for help.

Practice: status reading

Run:

git status

Write down:

Current branch:

Untracked files:

Modified files:

Staged files:

What command is Git suggesting?

Do not commit yet. The next lesson covers diff, staging, and the first commit.

Next: Git 103 - diff, add, commit, log.