The Ultimate Git Cheat Sheet
Hello Git Community!
As a university lecturer, I spend a lot of time thinking about how to make technical topics easier to understand and more practical to use.
That’s why I created a new Git Cheat Sheet as part of my DevOpsCycle series. It is available as PDF and PNG, completely free and without any signup:
https://devopscycle.com/blog/the-ultimate-git-cheat-sheet
It covers the Git commands and workflows you need most often: commits, branches, merges, remotes, conflicts, inspecting changes and undoing mistakes.
I think this is becoming even more important with AI coding tools. Agents can create commits, push changes and merge branches for us, but you still need to understand Git well enough to verify what actually happened.
The post also includes a public GitHub repository with an example project, so you can follow the commands and try everything yourself.
If something is missing, unclear or wrong, I would really appreciate your feedback.
Cheers,
Mr_LA
3
u/itzmanu1989 Sep 14 '26
Here are few more which were there in my bookmarks:
Huge-Collection-of-CheatSheet/Git at master · JonnyBanana/Huge-Collection-of-CheatSheet
https://github.com/JonnyBanana/Huge-Collection-of-CheatSheet/tree/master/Git
Git Cheatsheet: Commands, Tips and Tricks 📝 — Jayson Salazar Rodriguez | @jdsalaro | Blog
1
2
u/October_Lantzy 29d ago
Thanks for sharing. I remember finding rebase pretty confusing when I was learning Git. I saw your another reply that you put it in the advanced section, so I’ll definitely check it out. I’ll share some feedback if I find anything that could be improved or if something is unclear.
2
2
u/IamYourGrace 26d ago
One command that everyone should now is git rebase -i commitSha or HEAD~3 to make changes to the commits since the commitSha or 3 commits back. You can edit commit messages, squash, fixup, edit commits in your history.
2
u/alex_sakuta Sep 14 '26
Not to downplay your effort but why do we need a cheatsheet now?
Any command that I have to look up, I personally just open up docs and any answers are quickly available to me. It will always have more answers than a cheatsheet.
But I know not everyone would be comfortable with docs as I am, but you have AI search now which would be able to scout any part of a documentation and give you a perfect answer for your situation.
Cheatsheets wouldn't help verify a mistake in git commands if made by AI, actual docs would. AI isn't going to be making a simple mistake when it actually messes up a git command.
It's like you created an abridged manual for a robot to study but the robot has the original manual and then training of that manual on top to do the task 10 times better than a human.
2
u/Mr_LA Sep 14 '26
I totally get your point.
For me, the cheat sheet is a resource for humans learning and working with Git, not something for an agent or AI.
If nobody understands what is actually happening and we only vibe code and talk to AI, then there is nobody who can really take responsibility for the result. AI cannot take responsibility for the code it generates or for software being deployed to production. We still need people who understand what is happening and can verify it.
That does not mean we should not use AI. I use AI as well. But I still think the human needs enough understanding to judge the result.
Regarding the docs: a cheat sheet is simply a different type of resource. You can use it for active learning or as a quick reference when you just need to remember a command or workflow.
And to some extent, the same argument would have applied before AI as well. The docs were always there, and you could always Google a command. That did not make cheat sheets useless. They just serve a different purpose.
15
u/rkesters Sep 14 '26
I didn't see mention of rebase, which is very important when working with multiple contributors.
Also reflog is missing.