DEV Community: Sakthivel R

Beyond the Basics: 10 Git Commands to Level Up Your Development Game

Sakthivel R — Sat, 26 Apr 2025 03:53:53 +0000

🚀 Level Up with These Essential Git Commands

Introduction

Git is an indispensable tool for developers across all domains. As someone who works with both data engineering and MERN stack development, I've found these Git commands to be incredibly useful in my daily workflow. Let's explore them together!

Must-Know Git Commands

1. 🔍 git diff

Purpose: Show changes between files, commits, or branches.

Usage: Compare your working directory with the index or a previous commit.

git diff

2. 📜 git log

Purpose: Display the commit history.

Usage: Track changes, find specific commits, or understand project history.

git log

3. 📥 git clone

Purpose: Clone a remote repository to your local machine.

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

4. ⬇️ git pull

Purpose: Fetch and merge changes from the remote repository to your current branch.

git pull origin main

5. ⬆️ git push

Purpose: Push your local commits to the remote repository.

git push origin main

6. 🕵️ git blame

Purpose: Show who last modified each line of a file and when.

Usage: Great for debugging or understanding change history.

git blame filename.txt

7. ⚔️ Merge Conflicts (Concept)

Note: Merge conflicts happen when two branches modify the same part of a file.

To simulate a merge conflict:

git checkout -b new-branch
# Make changes, commit them
git checkout main
# Make conflicting changes
git merge new-branch
# Conflict occurs here

You'll need to manually resolve the conflict in the files and commit the resolution.

8. 🌿 git branch

Purpose: List, create, or delete branches.

git branch           # List branches  
git branch feature   # Create a branch  
git branch -d feature  # Delete a branch

9. 🚀 git checkout -b

Purpose: Create and switch to a new branch in one step.

git checkout -b new-feature-branch

10. 📁 .gitignore

Purpose: Tell Git which files or folders to ignore in version control.

Steps to set up:

Create a .gitignore file in your root directory.
Add patterns of files or folders to ignore.

Example:

*.log
node_modules/
.env

No command is needed — Git will automatically skip tracking files that match the patterns.

Practical Workflow Examples

Here's how these commands fit into a typical development workflow:

Start a new project:

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

Create a feature branch:

   git checkout -b new-feature

Make changes and check differences:

   # After editing files
   git diff

Commit your changes:

   git add .
   git commit -m "Add new feature"

Push to remote:

   git push origin new-feature

Keep your branch updated:

   git pull origin main

Investigate issues:

   git blame problematic-file.js

Conclusion

These Git commands have become essential tools in my development workflow. Whether you're working on MERN applications or data engineering projects, mastering these Git techniques will dramatically improve your efficiency and collaboration capabilities.

What Git commands do you find most useful in your projects? Let me know in the comments!

Written by Sakthivel R

Data Engineer | MERN Stack Developer

Step-by-Step Git Commands for First-Time Repo Setup(with GitHub)

Sakthivel R — Thu, 24 Apr 2025 04:58:23 +0000

🚀 Git- Git Basics for Beginners

*👨‍💻 By Sakthivel R

Hey developers! 👋

Here’s a beginner-friendly walk-through of basic Git commands, perfect if you're just starting out or brushing up for placements or projects. This was part of my Day assignment, and I thought it’d be helpful to share it with the dev community too. Let’s go! 💻✨

🔧 Step-by-Step Git Commands

1️⃣ Initialize a Git Repository

git init

This command initializes a new Git repository in your current directory. For example, it creates a repo in a folder like 24MCR086.

2️⃣ Add a File to Staging Area

git add 24MCR086.txt

This stages a specific file (24MCR086.txt) for commit.

Want to stage everything in the folder? Use:

git add .

3️⃣ Commit the File

git commit -m "Added Personal Details"

This creates a commit with a custom message. Make your commit messages meaningful so others can follow your changes easily.

4️⃣ Check Git Status

git status

This shows the current state of your working directory and staged files. For example, it will show if 24MCR086.txt is modified but not staged.

5️⃣ View Commit Log

git log

Want to see the history of commits? This command displays all your previous commits.

6️⃣ Add Remote GitHub Repository

git remote add origin https://github.com/DeveloperSakthi/24MCR086.git

This links your local Git repo to a remote GitHub repository. (Replace with your repo URL.)

7️⃣ Check the Current Branch

git branch

Displays your current branch. Initially, it might show master.

8️⃣ Rename Branch from master to main

git branch -M main

Renames the current branch from master to main.

Want to rename back to master? You can use:

git branch -M master

9️⃣ Set Global Git Config (One-time Setup)

git config --global user.email "sakthivelravi9894@gmail.com"
git config --global user.name "DeveloperSakthi"

This sets your identity for all Git projects on your system. You only need to do this once!

🔟 Push Code to Remote Repo

git push -u origin main

Pushes the local main branch to GitHub and sets it to track the remote branch.

🔁 Making More Changes?

Once you've made more changes or added new files, you can follow this pattern again:

git add .
git commit -m "Your next update message"
git push origin main

💡 Final Thoughts

That’s it for Day 1! These are your Git essentials. Trust me, once you get these basics down, version control becomes your best friend — especially in collaborative coding or project development 🚀

If you found this helpful or want me to share more Git or dev-related content, drop a ❤️ or comment!

Happy coding! 👨‍💻💥

– Sakthivel R