🚫 What is .gitignore?

When you're working with Git, not everything in your project should be tracked — things like compiled files, logs, environment variables, and node modules are usually not meant to be version controlled.

That’s where .gitignore comes in.

It’s a special file that tells Git:

👉 "Ignore these files and folders."

Example: .gitignore file for a Node.js project

node_modules/
.env
dist/
*.log

Explanation:

• node_modules/ — dependencies you install locally.
• .env — sensitive config like API keys.
• dist/ — output folder from build process.
• *.log — any log files.

⚠️ Important Tip:
.gitignore only works before files are tracked. If you accidentally committed something already, run:

git rm --cached filename

to untrack it, then commit again.

Why it Matters:

• Keeps your repo clean.
• Prevents committing sensitive data.
• Reduces repo size and clutter.
• Helps teams avoid conflicts.

Want More Git Tips?

Check out our other posts at readmebuddy.com/posts — we're sharing practical Git tricks, workflows, and tools to level up your development process.