By Ashish V Butle in DevSecOps —

"Code, Commit, Conquer: The Ultimate Git Tutorial for DevOps"

"Code, Commit, Conquer: The Ultimate Git Tutorial for DevOps"

🔧 Step 1: Setup Your Cyber Arsenal

💡
sudo apt update && sudo apt install git -y

Check installation:

💡
git --version
Just to flex. You need to know which version of your sword you’re swinging. 🔪

🧑‍💻 Step 2: Set Git Identity

💡
git config --global user.name "Your Name"
git config --global user.email "email@example.com
So Git knows who to blame when things go wrong. This is your digital fingerprint, cyber-ninja. 🔍

🗂️ Step 3: Initialize the Battlefield

💡
cd ~/Python && git init
Boom 💥 — now your folder is under surveillance. Every change is tracked like a suspicious login attempt at 3 a.m.

🔑 Step 4: Set Up SSH With GitHub

Now go to GitHub → Settings → SSH and GPG Keys and paste it like a pro.

💡
cat ~/.ssh/id_rsa.pub

Already done ✅ (You rock). To confirm:

💡
ssh -T [email protected]
You’re testing the connection. GitHub replies like a wise old sensei: "You've successfully authenticated." 🧙‍♂️

☁️ Step 5: Connect to GitHub Repo

Create a new repo on GitHub — leave it empty (no README, no .gitignore).

Then connect:

💡
git remote add origin [email protected]:Ashish-butle/Python.git
Adds the GitHub repo as a remote so you can push code into the cloud like magic.

To verify:

💡
git remote -v

💾 Step 6: Save and Upload Your Work (So You Don’t Lose It When Your Laptop Explodes)

💡
git add .
git commit -m "My glorious Python scripts. Let the world admire."
git branch -M maingit branch -M main
git push -u origin maingit push -u origin main
Stages all your work. Like packing your code into a suitcase before the trip.
Then git commit is your secure checkpoint — a snapshot before the code apocalypse. 🧨
Renames the default branch to main (modern times, people), and pushes it to GitHub.

🌿 Step 7: Work on a Separate Branch (So You Don’t Break the Main One)

💡
git branch -c sprint1
Creates a new branch for testing. Think of it as a playground where you can mess things up safely.

List all branch

💡
git branch -a
Lists all branches, including that one you forgot you made.

📋 Step 8: Push Your Changes (Hopefully After They Work)

💡
git checkout sprint1

Added some text and files

Tells you what’s changed, because guessing is not a best practice.

💡
git status
Tells you what’s changed, because guessing is not a best practice.

Stages, commits, and pushes your changes. This is your “Hey GitHub, look what I made!” moment.

💡
git add .
Stages all your work. Like packing your code into a suitcase before the trip.

Commits (saves) the changes with a message. Make it useful, or your future self will regret it.

💡
git commit -m "new changes"
Then git commit is your secure checkpoint — a snapshot before the code apocalypse. 🧨

Renames the default branch to main (modern times, people), and pushes it to GitHub.

💡
git push origin sprint1

🔁 Step 9: Merge Branches (Without Causing a Code Meltdown)

💡
git switch main

Merges your work from sprint1 into main. Be sure to test first, or your teammates might hunt you down.

💡
git merge sprint1

Now we are pushing to the main branch

💡
git push origin main

Git status

💡
git status

🕰️ Step 10: See What Happened (Because Memory is Overrated)

💡
git log --oneline

👯 Step 11: Clone or Update Code (Because Copy-Paste Only Works Locally)

💡
git clone git@github.com:Ashish-butle/Python.git

Makes a full copy of the repo on your machine. The legal way to “steal” code.

🔁 Pulling Updates

💡
git pull origin main
Gets the latest updates from GitHub. Do this often, or enjoy merge conflicts.

🛠️ Step 12: Fix Mistakes (Because Mistakes Will Happen)

Undo local changes: Restores the file to the last committed state. Like Ctrl+Z, but cooler.

💡
git restore filename.py

Unstage a file: you accidentally added. We’ve all been there.

💡
git reset filename.py

Undoes a bad commit safely by making a new one. Recommended for public repos.

💡
git revert <commit id>

Goes back in time and deletes history. Use only if you really mean it — no takebacks.

💡
git reset --hard <commit id>

🚀 Conclusion

Git is your time machine, project manager, and panic button — all in one.
Start small, commit often, and remember: git status is your best friend when things go weird.

Previous

DNS Records: The Mysterious Scrolls That Control the Internet😶‍🌫️