$ git log --oneline
Git is easier when you can see the repository change. GitGuide pairs concise explanations with interactive diagrams so commands become a mental model, not a list to memorize.
PROJECT HISTORY
A command can succeed while its effect stays mysterious. GitGuide was started to close that gap: show the state before, run the real command, and make the resulting change unmistakable.
9fc04c1 problem
The hard part was understanding what Git changed, where it changed, and what would happen next.
DESIGN PRINCIPLES
Every lesson begins with what changed in the repository, then connects that change to the command that caused it.
Files, commits, branches, and remotes build on the same visual language, so each new idea has somewhere familiar to land.
The visuals simplify the explanation, not Git itself. Learners still practice the commands and options used in real projects.
NOW / NEXT
YOUR NEXT COMMIT
Pick the situation that sounds most familiar. GitGuide will take you to the lesson that builds the right mental model first.
Start with repositories and commits, then see how Git records checkpoints without changing the way you edit files.
Open Git BasicsCREATED BY
A software engineer who enjoys turning difficult systems into dependable, understandable tools. GitGuide is an independent learning project shaped by that same goal: make the hidden parts of software easier to reason about.
Project Repository
github.com/twok-teks/git-guide