Amr Abdelkarem’s Post

If you use git in the terminal (that's where my claude code/opencode lives!), you've probably tried git log --graph --all and found it... hard to read. Serie renders a proper visual commit graph right in your terminal — with smooth branch lines, colors, and a TUI for browsing commits and diffs. Install: brew install serie Use: just run serie in any git repo. I also set up a short git alias for it: git config --global alias.lg '!serie' So now git lg gives me a beautiful branch visualization without leaving the terminal. Requires a terminal with image protocol support (iTerm2, Kitty, Ghostty). Doesn't work inside tmux unfortunately. https://lnkd.in/gpUPY2p7 #git #cli #devtools #terminal

A complete Git Commands Cheat Sheet for developers. From setup to branching, commits, and remote repositories. Perfect for beginners and quick revision. Here are the 15 most used Git commands: ✅ git init – Create a new Git repository ✅ git clone <url> – Copy a repository from GitHub ✅ git status – Check file status in the repo ✅ git add <file> – Add a file to staging area ✅ git add . – Add all files to staging ✅ git commit -m "message" – Save changes with a message ✅ git log – Show commit history ✅ git log --oneline – Short commit history ✅ git diff – Show changes in files ✅ git branch – List branches ✅ git branch <name> – Create a new branch ✅ git checkout -b <name> – Create & switch to a branch ✅ git push origin <branch> – Upload code to remote repository ✅ git pull origin <branch> – Download latest updates ✅ git stash – Temporarily save uncommitted changes Save it now and keep learning every day. #Git #VersionControl #SoftwareDevelopment #JavaDeveloper #WebDevelopment #DevOps #CodingJourney

Git isn’t scary — it’s your personal time machine for code! ⏳ Start here in 60 seconds: • git status → what’s going on? • git add . → stage your changes • git commit -m "Feature: awesome" → lock it in history • git push → share the victory Want step-by-step explanations, visuals, and the 10 commands every beginner actually needs? I just published a beginner-friendly guide: https://lnkd.in/gumP6k64 Save it, share it, level up! 🚀 Hitesh Choudhary #GitBasics #DeveloperJourney #TechTips [Blog 1]

A Quick Guide to Important Git Commands:- 🔹 git stash – Temporarily save uncommitted changes so you can switch branches safely. 🔹 git stash pop – Restore the latest stashed changes and remove them from the stash list. 🔹 git merge – Combine changes from one branch into another branch. 🔹 git commit --amend – Modify the last commit (update message or add missed files). 🔹 git log – View the commit history of the repository. 🔹 git cherry-pick – Apply a specific commit from another branch. 🔹 git reset --soft – Move to a previous commit but keep changes staged. 🔹 git reset --hard – Move to a previous commit and discard all changes after it. 🔹 git rebase – Reapply commits on top of another branch to maintain a cleaner history. Small commands, but they make a big difference in day-to-day development workflows. #Git #VersionControl #SoftwareDevelopment #FrontendDevelopment #Developers

Most beginners use Git only for commit and push. But a few powerful commands can literally save hours of work. Here are 3 Git commands every developer should know: 1️⃣ git stash Sometimes you are working on something but suddenly need to switch branches. Instead of committing unfinished code, just run: git stash This temporarily saves your changes so you can switch branches safely. When you're ready to get your changes back: git stash pop Super useful when you're in the middle of something. 2️⃣ git log --oneline Ever tried to find a previous commit and got lost in a huge Git log? Use: git log --oneline It shows a clean, short history of commits, making it much easier to navigate. 3️⃣ git checkout -b branch-name Instead of creating and then switching branches separately: git branch feature-login git checkout feature-login Just do it in one command: git checkout -b feature-login Faster and cleaner. Small Git tricks like these can make your workflow much smoother. What’s your most used Git command? 👇

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

Few Git related questions: 1) What are Git tags? 🔖 -- Git tags are like bookmarks of a specific point in git history.There are multiple commits in git and if we want to mark a specific point then we can use git tags. 2) How to combine multiple Git commits into a single commit ? -- Using Git rebase command 3) How to ignore pushing changes to a file to Git? 📃 -- using .gitignore -> tells git which files and folders to ignore. 4) Purpose of .git folder ? 📁 -- It is a hidden directory and has information about commit history, branches, configuration , tags etc

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 Swadesh Kumar for more such content 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

Git rebase vs. git merge debate shouldn't be about which is "better"; it should be about when and how to use each. While Rebase can be dangerous, there is a Safe Zone where it significantly improves code quality without any risk. Here is how we can use it: 1- The "Local Cleanup": Before pushing our code for review, we use rebase -i (interactive) to squash our "work in progress" and "typo fix" commits. The team sees one clean, logical commit instead of our messy 2-hour struggle. 2- The "Stale Branch" Update: If let’s say a feature/fix branch is two weeks old, rebasing it against the latest main ensures the testing of the logic against today's code, not last month’s. 3- Never use --force push, because this can affect the work of your teammates if they worked on the same branch. However, the reason many avoid Rebase is that it rewrites history. When you rebase a shared branch, you are deleting the "truth" of when and how code was written, which can make audits a nightmare. Furthermore, if you rebase incorrectly, you can fall into "Conflict Hell"—where you’re forced to fix the same conflict for every single commit in your chain.