How to Use Git for IT Professionals

Git Mastery: From Novice to Expert - A Technical Deep Dive and Roadmap Roadmap to Git Mastery: 1. Fundamentals    - Basic commands: init, add, commit, push, pull    - Understanding the working directory, staging area, and repository    - Branching and merging basics 2. Intermediate Concepts    - Rebasing vs. Merging    - Interactive rebasing    - Cherry-picking    - Reflog for recovery    - Stashing changes 3. Advanced Git    - Submodules and subtrees    - Git hooks    - Custom Git commands    - Git internals: objects, refs, and packfiles    - Git attributes and smudge/clean filters 4. Collaboration and Workflow    - Pull requests and code review processes    - Git flow vs. GitHub flow vs. GitLab flow    - Handling merge conflicts efficiently    - Conventional commits and semantic versioning 5. Git at Scale    - Monorepos vs. multi-repo strategies    - Git LFS for large files    - Shallow clones and partial clones    - Optimizing Git performance for large repositories Advanced Git Commands and Techniques: 1. Bisecting: 𝚐𝚒𝚝 𝚋𝚒𝚜𝚎𝚌𝚝 𝚜𝚝𝚊𝚛𝚝 <𝚋𝚊𝚍> <𝚐𝚘𝚘𝚍>    Use binary search to find the commit that introduced a bug. 2. Debugging with Git:    𝚐𝚒𝚝 𝚋𝚕𝚊𝚖𝚎 -𝙻 <𝚜𝚝𝚊𝚛𝚝>,<𝚎𝚗𝚍> <𝚏𝚒𝚕𝚎>    𝚐𝚒𝚝 𝚕𝚘𝚐 -��� <𝚜𝚝𝚛𝚒𝚗𝚐> --𝚙𝚊𝚝𝚌𝚑 3. Rewriting history:    𝚐𝚒𝚝 𝚛𝚎𝚋𝚊𝚜𝚎 -𝚒 𝙷𝙴𝙰𝙳~<𝚗>    𝚐𝚒𝚝 𝚌𝚘𝚖𝚖𝚒𝚝 --𝚊𝚖𝚎𝚗𝚍    𝚐𝚒𝚝 𝚏𝚒𝚕𝚝𝚎𝚛-𝚋𝚛𝚊𝚗𝚌𝚑 4. Reflog for recovery:    𝚐𝚒𝚝 𝚛𝚎𝚏𝚕𝚘𝚐 𝚜𝚑𝚘𝚠 <𝚋𝚛𝚊𝚗𝚌𝚑>    𝚐𝚒𝚝 𝚛𝚎𝚜𝚎𝚝 --𝚑𝚊𝚛𝚍 <𝚋𝚛𝚊𝚗𝚌𝚑>@{<𝚗>} 5. Advanced merging:    𝚐𝚒𝚝 𝚖𝚎𝚛𝚐𝚎 --𝚜𝚚𝚞𝚊𝚜𝚑 <𝚋𝚛𝚊𝚗𝚌𝚑>    𝚐𝚒𝚝 𝚖𝚎𝚛𝚐𝚎 -𝚇 𝚒𝚐𝚗𝚘𝚛𝚎-𝚜𝚙𝚊𝚌𝚎-𝚌𝚑𝚊𝚗𝚐𝚎 <𝚋𝚛𝚊𝚗𝚌𝚑> 6. Submodules:    𝚐𝚒𝚝 𝚜𝚞𝚋𝚖𝚘𝚍𝚞𝚕𝚎 𝚊𝚍𝚍 <𝚛𝚎𝚙𝚘_𝚞𝚛𝚕>    𝚐𝚒𝚝 𝚜𝚞𝚋𝚖𝚘𝚍𝚞𝚕𝚎 𝚞𝚙𝚍𝚊𝚝𝚎 --𝚒𝚗𝚒𝚝 --𝚛𝚎𝚌𝚞𝚛𝚜𝚒𝚟𝚎 7. Git hooks:    Customize in .𝚐𝚒𝚝/𝚑𝚘𝚘𝚔𝚜/    Example: pre-commit for linting 8. Plumbing commands:    𝚐𝚒𝚝 𝚌𝚊𝚝-𝚏𝚒𝚕𝚎 -𝚙 <𝚘𝚋𝚓𝚎𝚌𝚝>    𝚐𝚒𝚝 𝚕𝚜-𝚝𝚛𝚎𝚎 <𝚝𝚛𝚎𝚎-𝚒𝚜𝚑>    𝚐𝚒𝚝 𝚛𝚎𝚟-𝚙𝚊𝚛𝚜𝚎 <𝚛𝚎𝚏> Deep Dive: Git Internals Understanding Git's object model is crucial: - Blobs: File contents - Trees: Directory structures - Commits: Snapshots with metadata - Tags: Named references to commits Core Concepts: 1. Distributed Version Control System (DVCS) 2. Snapshots, not differences 3. Nearly every operation is local 4. Git has integrity (SHA-1 hash) 5. Git generally only adds data Pro Tips: 1. Use 𝚐𝚒𝚝 𝚌𝚘𝚗𝚏𝚒𝚐 --𝚐𝚕𝚘𝚋𝚊𝚕 𝚊𝚕𝚒𝚊𝚜.<𝚊𝚕𝚒𝚊𝚜-𝚗𝚊𝚖𝚎> '<𝚐𝚒𝚝-𝚌𝚘𝚖𝚖𝚊𝚗𝚍>' for custom shortcuts. 2. Leverage 𝚐𝚒𝚝 𝚠𝚘𝚛𝚔𝚝𝚛𝚎𝚎 for managing multiple working copies. 3. Implement a commit message convention (e.g., Conventional Commits) for clarity and automation. 4. Use 𝚐𝚒𝚝 𝚏𝚎𝚝𝚌𝚑 --𝚊𝚕𝚕 --𝚙𝚛𝚞𝚗𝚎 regularly to keep your local references clean. 5. Master 𝚐𝚒𝚝 𝚛𝚎𝚋𝚊𝚜𝚎 --𝚘𝚗𝚝𝚘 for complex branch management. What's your biggest Git challenge?

Whether you’re a MLE or data scientist, or system admin, you should know about Git. It helps with: - Collaboration – Work seamlessly with teams across the globe. - Version Control – Track changes and roll back mistakes. - Code Safety – Keep backups and sync your work across devices. -- Setting Up a New Repository git init # Initialize a new Git repository git add --all # Stage all changes git commit -m "Initial commit" # Commit changes with a message git remote add origin <URL> # Link to remote repository git push -u origin master # Push to remote repository -- Working with Changes git status # Check the current status git add <file> # Stage specific file git add -p <file> # Stage changes interactively git commit -m "Your message" # Commit changes -- Viewing History git log # View commit history git log -p <file> # View history of a specific file git blame <file> # See who modified each line -- Branching & Merging git branch -av # List all branches git branch <new-branch> # Create a new branch git checkout <branch> # Switch to a branch git merge <branch> # Merge a branch into the current one -- Undoing Changes git reset --hard HEAD # Reset all changes to last commit git checkout HEAD <file> # Revert file to last committed state git revert <commitID> # Revert a specific commit -- Cloning & Pulling from Remote git clone <URL> # Clone a repository git pull origin master # Fetch & merge latest changes git push origin <branch> # Push changes to remote -- Stashing Changes git stash # Temporarily save changes git stash list # View all stashes git stash apply # Apply latest stash git stash drop # Delete latest stash -- Tagging git tag <tag-name> # Create a new tag git tag # List all tags git push origin <tag-name> # Push tag to remote -- Viewing Differences git diff # Show unstaged changes git diff HEAD # Compare working directory to last commit -- Deleting Branches git branch -d <branch> # Delete a local branch (if merged) git branch -D <branch> # Force delete a branch -- Working with Remotes git remote -v # List all remote repositories git remote add <name> <URL> # Add a new remote git remote remove <name> # Remove a remote repository Alex Lavaee added in the comments: I like to add these to my ~/.bashrc or ~/.zshrc configuration. Here's an example of something to add: ```bash alias gs="git status" alias gp="git push" alias gac="git add . && git commit -m" alias gcm="git commit -m"

Git Lifecycle for Data Engineers: Think in Pipelines ⚙️ From dev to production, Git is the “Data Lineage” for your infrastructure. If you build data pipelines, you already understand Git. The flow is almost the same. 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆 Your raw zone. Files change, experiments happen, nothing locked yet. 𝗦𝘁𝗮𝗴𝗶𝗻𝗴 𝗔𝗿𝗲𝗮 git add marks what should move forward. Like selecting the clean batch before loading. 𝗟𝗼𝗰𝗮𝗹 𝗥𝗲𝗽𝗼 git commit -m "msg" stores a snapshot. Clear history. Easy rollback. 𝗥𝗲𝗺𝗼𝘁𝗲 𝗥𝗲𝗽𝗼 Shared source of truth. git push sends your work. git pull syncs with the team. Know these common commands you’ll use daily: • git add → stage changes • git commit -m → save snapshot • git commit -a -m → stage + commit tracked files • git push → send to remote • git fetch → download updates only • git pull → fetch + merge • git merge → combine branches • git diff → inspect changes anytime Image Credits: Brij kishore Pandey Follow the Data engineers rule: Commit like pipeline checkpoints — small, clear, reversible. Version control isn’t just for devs. It’s how data teams ship with confidence. 🔁

Most people don’t struggle with Git. They struggle with the workflow. You learn commands like: git add git commit git push But still feel confused. Because Git is not about commands. It’s about understanding the flow. Modify → Stage → Commit → Push Once this clicks… everything becomes simple. 🔥This PDF explains Git the way it should be learned: • What Git actually does (version control) • Difference between Git and GitHub • How changes are tracked step-by-step Then builds the real workflow: • Initial setup (config, init) • Staging vs committing • Viewing history (log, status) • Working with branches • Merging changes And the part most people struggle with: • Connecting local repo to GitHub • Push, pull, clone • Working with remote repositories Plus something very important: Undoing mistakes. • Revert • Reset • Amend Because that’s what you’ll actually need in real work. These are not just commands. It’s clarity. A simple way to use this: 1. Don’t memorize commands 2. Understand the flow 3. Practice on a small project 4. Break things → fix them That’s how Git actually clicks. Save this — you’ll revisit it again and again. Follow Sahil Hans for more! 🤝

Git is used by over 150 million engineers worldwide, yet some engineers cannot remember 4-5 commands during a crisis that could save them. A few years back, I was mentoring an intern and he accidentally deleted the main branch on the project he was working. He spent 2 hours googling his way through a disaster that should have taken 60 seconds to fix. For an intern, this is common and part of their learning curve. But for a mid-level engineer who has 2 to 3 years of experience this shouldn't be acceptable. If you are a software engineer, you need to understand the safety nets built into your version control. ➤ [1] The Git Reflog If you delete a branch on your local machine, it isn't actually gone. Git records every move you make, even the mistakes. 1) Run 'git reflog' to see the history of your HEAD pointer. 2) Find the commit hash from right before the deletion. 3) Use 'git checkout' to jump back to that specific moment. This is the ultimate undo button. Unless you’ve manually cleared your cache, your work is usually sitting there waiting to be found. ➤ [2] Reset vs Revert You have to decide if you want to change the past or create a new entry in the future. 1) 'git reset' is for local mistakes you haven't pushed yet. 2) 'git revert' is for mistakes that are already on the shared server. 3) Resetting a public branch breaks the state for everyone else on the team. Think of Revert as a "reverse commit." It keeps the history clean and ensures your teammates don't end up with a broken repository. ➤ [3] Force Push Safety Force pushing is useful but dangerous. If you do it wrong, you overwrite the work of everyone else on the branch. 1) Standard 'git push --force' is the "nuke" option. 2) 'git push --force-with-lease' is the professional alternative. 3) It checks if anyone else has pushed code since your last pull. If someone else has added code, the command fails instead of deleting their work. It’s a simple habit that prevents massive team arguments. ➤ [4] Branch Protection You shouldn't rely on your memory to protect the main branch. Use the settings in GitHub or GitLab to do the work for you. 1) Lock the main branch so no one can push to it directly. 2) Require at least one Pull Request review before merging. 3) Turn off the ability to force push for everyone on the team. Senior engineers build environments where a single mistake can't take down the project. Git was designed to be hard to break, but you have to look under the hood. Stop memorizing commands and start understanding how the system works. Mastering recovery will save you when the deadline is hitting.