Mastering Git Branching & GitHub Workflow

Focused on learning and practicing Git & GitHub properly. Instead of just writing code, I worked on managing it the right way. ✔ Creating and configuring Git ✔ Working with local & remote repositories ✔ init, clone, status ✔ add, commit, push ✔ Branching & merging ✔ Handling merge conflicts ✔ Understanding workflow & forking Realization: Writing code is easy. Managing code is what makes you a developer. Next milestone: Use Git in every single project — no excuses. #Git #GitHub #VersionControl #ProgrammingJourney #Cpp #LearningInPublic

🚀 Day 1 of My GitHub Journey — Understanding the Basics Today wasn’t just about running commands… it was about actually understanding what each one does. Small clarity now saves big headaches later. Here’s what I learned 👇 🔹 git --version Checks whether Git is installed and shows the current version. 🔹 git config --global user.name "Your Name" Sets the username that will appear in your commits. 🔹 git config --global user.email "your@email.com" Sets the email linked to your commits. 🔹 git config --list Displays your current Git configuration settings. 🔹 git init Initializes a new Git repository in your project folder. 🔹 git clone <repo-url> Downloads an existing repository from GitHub to your local machine. 🔹 git status Shows the current state of your repo — what’s changed, staged, or untracked. 💡 Biggest takeaway: Git isn’t scary… it just wants you to be precise. Day 1 done. Back again tomorrow to go deeper. 💻🚀 #Git #GitHub #LearningInPublic #DeveloperJourney #VersionControl

Exploring the basics of Git and GitHub today. Learning how Git helps track code changes and how GitHub makes collaboration easier for developers was really interesting. Understanding concepts like repositories, push, pull, and Git architecture (working tree, staging area, and repositories) gives a clear idea of how real-world development teams manage their code. Small steps in learning version control can make a big difference in becoming a better developer. #Git #GitHub #VersionControl #SoftwareDevelopment #CodingJourney #DeveloperSkills #TechLearning

I have been trying to get more comfortable with Git beyond just add, commit, and push, so I built something small to practice. It’s a simple CLI-based Git tutor powered by Gemini. You can ask it questions like “what is git commit” and it explains along with the actual commands. But the main goal wasn’t just the AI part. I wanted to practice how real projects are managed, so I used a proper workflow with dev → staging → main and created PRs for every change. It’s a simple project, but it helped me understand Git in a much more practical way. 👉 GitHub Repo: https://lnkd.in/dukVfX4d #Python #Git #GitHub #LearningJourney

Hi developers..💻 Hope you all had a productive and positive week 🚀 Continuing from last weekend’s Git commands post… Last time, I shared some essential Git commands every developer should know. But knowing commands is just the first step — understanding when and why to use them is what truly builds confidence. Let’s quickly revisit the some more 👇 📌 I’m also attaching a small Git basics file for reference. You can save it and revise along with me. **No pressure. **No rush. **Just consistent learning. Once we are comfortable with Git & GitHub, 👉 Next step: Bitbucket and real-time project usage. Let’s grow together 🚀 Who is in? 🙌 If you want pdf comment👇 just "GBG" I'll share to you📄. #Git #GitHub #Bitbucket #VersionControl #WeekendLearning #LearnInPublic #SoftwareDevelopment

🚀 Day 23 of #90DaysOfDevOps Today, I leveled up from simple commits to the most powerful concept in Git: Branching & GitHub Workflows. 🌿 Isolation is key in DevOps💻—you never want to experiment on your production-ready code. Today, I mastered how to keep the "Source of Truth" safe while building new features. What I practiced: ✅ Feature Branching: Created feature-1 and feature-2 to work on updates without breaking the main branch. ✅The Modern Switch: Transitioned from git checkout to git switch—the cleaner, dedicated way to navigate between branches. ✅Remote Architecture: Finally demystified the relationship between Origin (my personal fork) and Upstream (the original source). ✅ Syncing Workflows: Learned the "Fetch + Merge" dance to keep my local environment perfectly aligned with the original repository. 💯 Key takeaway: Understanding the difference between git fetch and git pull is a game-changer. Fetching gives you that "buffer zone" to review changes before they merge into your local work, ensuring a conflict-free and stable pipeline. ⚡ #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Git #GitHub #Linux #OpenSource #LearningInPublic #CloudComputing

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you ....... If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Vishakha Singhal ❤️ Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. 👇Bonus Tips : ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use .gitignore to avoid uploading junk files

Once I understood the core commands, everything changed, here is the GitHub Crash Course for you ....... If you're still stuck on "how to use GitHub properly"? Here's a simple breakdown that helped me (and will help you too): - Repository = Project folder (local or remote) - Commit = Save a snapshot of your changes - Branch - Parallel version of your project - Merge = Combine branches - Clone / Push/Pull = Sync local and remote repos Most Useful Git Commands (with purpose): git init: # Start a new Git repo git clone <url>: # Copy repo to your local system git status: # See current changes git add.: # Stage all files for commit git commit -m "msg": # Save changes with message git push: # Upload changes to GitHub git pull: # Fetch latest from GitHüb git branch: # List branches git checkout -b dev: # Create & switch to new branch git merge dev: # Merge dev into main Connect Vishakha Singhal ❤️ Repost it to share in your network Save it if you don't wanna miss it Comment "GitHub" & I'll DM it to you directly. 👇Bonus Tips : ✅ Always write meaningful commit messages ✅ Never push directly to main in a team project ✅ Use .gitignore to avoid uploading junk files

Today’s Learning: Git vs GitHub In today’s class, I learned the difference between Git and GitHub. 🔹 Git is a version control software installed locally to track changes in code. 🔹 GitHub is a web-based platform that hosts Git repositories and enables collaboration. Understanding this difference cleared a major confusion for me. From tomorrow, I’m starting hands-on practice to apply these concepts. #Git #GitHub #VersionControl #SoftwareDevelopment #LearningJourney

I was up at 2AM going through Git fundamentals and something finally clicked. Git doesn't save files. It saves snapshots. That distinction matters more than it sounds. If a file hasn't changed, Git just links to the previous version instead of duplicating it. The whole system is built around efficiency and history, not just backup. The mental model that helped me most: • Working Directory = your draft • Staging Area = what you're deciding to commit to • Commit = the permanent record Once I stopped thinking of it as "saving" and started thinking of it as "documenting a decision," branching and pull requests made way more sense, too. Still a lot to learn, but late nights like this are starting to feel less like grinding and more like building something. Does anyone else find that one reframe made a whole concept land differently?