If you want to create repo history without crying later this guide will help. This short git tutorial covers git init on the command line and walks you through the initial commit and adding a git remote. It is practical and mildly sarcastic but accurate which is the good kind of mean.

Why start with git init

git init is the simplest way to bring version control to a project folder. It makes a hidden .git folder where Git stores all the metadata that tracks changes and saves you from manually rewriting history when things go wrong. That day will come. Be ready.

Prepare the project folder

Open your terminal and change directory to the folder you want to track. The repository lives where you run git init so pick the right spot and try not to make your downloads folder a Git graveyard.

Quick checks

• Confirm you are in the intended folder with pwd or ls
• Set identity if needed with git config user.name "Your Name" and git config user.email "you@example.com"

Initialize the repository

Run the command that actually creates the repo.

git init

That creates a .git folder that Git will use to track your files. No drama now, only future responsibility.

Create a sensible ignore file

Before you stage everything take a second to create a .gitignore. This keeps build artifacts user secrets and other trash out of your repo. You get to avoid shame and your coworkers will thank you in passive aggressive comments.

# Example entries
node_modules/
.env
dist/
*.log

Stage and make the initial commit

Staging selects what goes into the first snapshot. Then commit with a clear message and modest pride.

git add .
git commit -m "Initial commit"

Good commit messages make future debugging less painful and your future self slightly less angry. Keep messages short and descriptive.

Add a remote and push if you want backup or sharing

If you plan to host the repo on a service add a remote and push the branch. Replace the URL with the one from your hosting service.

git remote add origin https://example.com/yourname/yourrepo.git
git push -u origin main

Note that some hosts still use master as the default branch name. Adjust the branch name if needed.

Useful tips from someone who learned the hard way

• Create the .gitignore before the first commit to avoid accidentally committing junk
• Use descriptive branch names that show purpose and avoid cryptic labels
• Sign commits or set up CI later if you care about provenance and automation
• Back up and push early to reduce the amount of crying required for recovery

This workflow gets you a working local repo and an optional remote with minimal fuss. It is the foundation of good version control practices and a must have among developer tools. Now that your repo exists you can branch work merge responsibly and pretend you always followed best practices.